svn commit: r326758 - in head/sys/i386: conf include

[Rodney W. Grimes]

...
> > 
> > We need to break the developers model that i386 is dead and that i386 is
> > not running on extremly modern hardware due to the factor of virtualization.
> > 
> > Output from one of my VM's running inside bhyve:
> > 
> >  # uname -a
> > FreeBSD filestore.dnsmgr.net 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 04:10:47 UTC 2017     root at releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386
> > 
> >  # dmesg | head -24
> > Copyright (c) 1992-2017 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> >         The Regents of the University of California. All rights reserved.
> > FreeBSD is a registered trademark of The FreeBSD Foundation.
> > FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017
> >     root at releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
> > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)
> > VT(vga): resolution 640x480
> > info: [drm] Initialized drm 1.1.0 20060810
> > CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.39-MHz K8-class CPU)
> This is quite old processor, IvyBridge is 6 generations old :).

I think you missed the point, this is a i386 guest running on an amd64
host inside of a hypervisor, bottom line, your gona see advanced amd64
features in i386 running in such situations, and we should probably stop
ignoreing this fact and embrace it as reality.

Another words you are going to see i386 running on the 6 generation newer
CPU that I dont have, and to say that this is unlikely is just a false
statement.

-- 
Rod Grimes                                                 rgrimes at freebsd.org