Skip to contentSkip to conversation

x86/microcode: Early load microcode

PATCH Jamie Gloudon 5 participants 12 messages Oct 1, 2012 – Dec 12, 2012

lore
Share & tools
lore

Jamie Gloudon

author
#0 lore raw

Hey,

Any chance of this getting merge for the 3.7 cycle?

Regards,
Jamie Gloudon

author
#2 lore raw

Seems like a better alternative to microcode_ctl which some distros don't contain.

Regards,
Jamie Gloudon

Quoted 14 lines · Borislav Petkov
Quoted 3 lines · Jamie Gloudon

Hey,

Any chance of this getting merge for the 3.7 cycle?

It is not ready yet: http://marc.info/?l=linux-kernel&m=134910582107898

Out of curiosity: why do you nee it?

Thanks.

Signature · 2 lines
Regards/Gruss,
Boris.
#3 lore raw
Quoted 4 lines · Jamie Gloudon
Quoted 3 lines · Borislav Petkov
Quoted 2 lines · Jamie Gloudon

Hey,

Quoted 8 lines
Quoted 6 lines
Quoted 1 line

Any chance of this getting merge for the 3.7 cycle?

It is not ready yet: http://marc.info/?l=linux-kernel&m=134910582107898

Out of curiosity: why do you nee it?

Seems like a better alternative to microcode_ctl which some distros don't contain.

[ Let me reorganize the mail chain as it should be,
without top-posting. Please try not to top-post:
http://curl.haxx.se/mail/etiquette.html#Do_Not_Top_Post ]

Well,

if you want to reload your microcode, you shouldn't be needing microcode_ctl (I believe this should be the case too on Intel, from staring at the code - on AMD it works).

Basically, you simply put the microcode binaries into /lib/firmware/{amd,intel}-ucode/ and then do as root:

$ echo 1 > /sys/devices/system/cpu/microcode/reload

That's it, no need for special tools.

Signature · 2 lines
Regards/Gruss,
    Boris.
author
#4 lore raw
Quoted 25 lines · Borislav Petkov
Quoted 4 lines · Jamie Gloudon
Quoted 3 lines · Borislav Petkov
Quoted 2 lines · Jamie Gloudon

Hey,

Quoted 8 lines
Quoted 6 lines
Quoted 1 line

Any chance of this getting merge for the 3.7 cycle?

It is not ready yet: http://marc.info/?l=linux-kernel&m=134910582107898

Out of curiosity: why do you nee it?

Seems like a better alternative to microcode_ctl which some distros don't contain.

[ Let me reorganize the mail chain as it should be,
without top-posting. Please try not to top-post:
http://curl.haxx.se/mail/etiquette.html#Do_Not_Top_Post ]

Well,

if you want to reload your microcode, you shouldn't be needing microcode_ctl (I believe this should be the case too on Intel, from staring at the code - on AMD it works).

Quoted 10 lines

Basically, you simply put the microcode binaries into /lib/firmware/{amd,intel}-ucode/ and then do as root:

$ echo 1 > /sys/devices/system/cpu/microcode/reload

That's it, no need for special tools.

Signature · 2 lines
Regards/Gruss,
    Boris.

My main interest was getting PEBS events support for perf on Intel SNB cpus. Loading the microcode at runtime was not going to work.

However, thanks for pointing me in the right direction. I notice today this is not the case anymore from the thread below.

http://marc.info/?l=linux-kernel&m=133905353211963&w=2

Regards,
Jamie Gloudon

#5 lore raw
Quoted 7 lines · Jamie Gloudon

My main interest was getting PEBS events support for perf on Intel SNB cpus. Loading the microcode at runtime was not going to work.

However, thanks for pointing me in the right direction. I notice today this is not the case anymore from the thread below.

http://marc.info/?l=linux-kernel&m=133905353211963&w=2

Yes, there's a perf callback from within the ucode driver to recheck PEBS. This is in 3.6 so PEBS should work there with the required ucode patch.

Signature · 2 lines
Regards/Gruss,
Boris.
#6 lore raw
In reply to Borislav Petkov
Quoted 7 lines · Borislav Petkov
Quoted 3 lines · Jamie Gloudon

Hey,

Any chance of this getting merge for the 3.7 cycle?

It is not ready yet: http://marc.info/?l=linux-kernel&m=134910582107898

Yes, Fenghua who has been working on it unfortunately got preempted at an inopportune moment. It will get fixed.

-hpa

Signature · 2 lines
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.
#7 lore raw
Quoted 6 lines · H. Peter Anvin
Quoted 5 lines · Borislav Petkov
Quoted 3 lines · Jamie Gloudon

Hey,

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

Any chance of this getting merge for the 3.7 cycle?

It is not ready yet: http://marc.info/?l=linux-kernel&m=134910582107898

Yes, Fenghua who has been working on it unfortunately got preempted at an inopportune moment. It will get fixed.

When he got interrupted did he have any beta patches to dracut that could be posted?

#8 lore raw
Quoted 14 lines · H. Peter Anvin
Quoted 10 lines · Borislav Petkov
Quoted 9 lines · Jamie Gloudon
Quoted 4 lines

Hey,

Any chance of this getting merge for the 3.7 cycle?

It is not ready yet: http://marc.info/?l=linux-

kernel&m=134910582107898

Quoted 2 lines
Quoted 1 line
Quoted 7 lines
Quoted 1 line

Yes, Fenghua who has been working on it unfortunately got preempted

at an

Quoted 1 line

inopportune moment. It will get fixed.

When he got interrupted did he have any beta patches to dracut that could be posted?

I'll post new patchset as soon as possible.

Thanks.

-Fenghua

#10 lore raw
Quoted 7 lines · H. Peter Anvin
Quoted 4 lines · Konrad Rzeszutek Wilk

When he got interrupted did he have any beta patches to dracut that could be posted?

To *dracut*?

The replacement for mkinitrd. You know the thing that creates your initramfs.cpio.gz.

#11 lore raw
Quoted 12 lines · Konrad Rzeszutek Wilk
Quoted 7 lines · H. Peter Anvin
Quoted 4 lines · Konrad Rzeszutek Wilk

When he got interrupted did he have any beta patches to dracut that could be posted?

To *dracut*?

The replacement for mkinitrd. You know the thing that creates your initramfs.cpio.gz.

Yes... it just seems that mucking with dracut is the last step in the chain. If your boot loader doesn't support initramfs concatenation, (a) complain to your bootloader author, (b) you can just use "cat"...

-hpa

Signature · 2 lines
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.