Armin K. wrote:
As for the microcode firmware, I too am an user of that. However,
I used Archlinux instructions for that and they recently switched
to "Early Microcode Loading", which means building the firmware
as an initramfs and loading it before the kernel starts (on the
first CPU only) due to issues on Haswell hardware. Mine is SandyBridge
and it receives and update and turns pebs on as a direct result of
that. It's worth noting that "Early Microcode Loading" requires the
microcode module to be built in, while the classic one requires it
to be built as module. This is what I see in my kernel:
[ 0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.19.0-krejzi ([email protected]) (gcc version
4.9.2 (Krejzi 4.9.2) ) #1 SMP PREEMPT Tue Feb 24 05:26:52 CET 2015
and further down:
[ 0.094496] CPU2 microcode updated early to revision 0x29, date = 2013-06-12
That's interesting. I took a look at my system and have:
[ 4.442331] microcode: CPU0 sig=0x306f2, pf=0x4, revision=0x29
[ 4.442559] microcode: CPU1 sig=0x306f2, pf=0x4, revision=0x29
[ 4.442788] microcode: CPU2 sig=0x306f2, pf=0x4, revision=0x29
[ 4.443022] microcode: CPU3 sig=0x306f2, pf=0x4, revision=0x29
[ 4.443253] microcode: CPU4 sig=0x306f2, pf=0x4, revision=0x29
[ 4.443483] microcode: CPU5 sig=0x306f2, pf=0x4, revision=0x29
[ 4.443712] microcode: CPU6 sig=0x306f2, pf=0x4, revision=0x29
[ 4.443939] microcode: CPU7 sig=0x306f2, pf=0x4, revision=0x29
[ 4.444170] microcode: CPU8 sig=0x306f2, pf=0x4, revision=0x29
[ 4.444398] microcode: CPU9 sig=0x306f2, pf=0x4, revision=0x29
[ 4.444627] microcode: CPU10 sig=0x306f2, pf=0x4, revision=0x29
[ 4.444855] microcode: CPU11 sig=0x306f2, pf=0x4, revision=0x29
[ 4.445107] microcode: Microcode Update Driver: v2.00
<[email protected]>, Peter Oruba
That's not early, but my bootscripts start somewhere around the 6.4 mark. I did
not do anything to load this microcode but it must be in the kernel tarball. I
can't even find an option to control this.
I don't know what good 'early loading would do. Would I save a half second?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
