Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1560975
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 01/13] x86/microcode/intel: Drop stashed AP patch pointer optimization |
| Date | 2017-01-17 21:10 +0100 |
| Message-ID | <t0IeS-358-7@gated-at.bofh.it> (permalink) |
| References | <t0FTI-1vq-27@gated-at.bofh.it> <t0G3n-1zz-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, 17 Jan 2017, Borislav Petkov wrote: > From: Borislav Petkov <bp@suse.de> > > This was meant to save us the scanning of the microcode containter in > the initrd since the first AP had already done that but it can also hurt > us: > > Imagine a single hyperthreaded CPU (Intel(R) Atom(TM) CPU N270 for > example) which updates the microcode on the BSP but since the microcode > engine is shared between the two threads, the update on CPU1 doesn't > happen because it has already happened on CPU0 and we don't find a newer > microcode revision. > > Which doesn't set the intel_ucode_patch pointer and at initrd > jettisoning time and we don't save the microcode patch for later > application. > > Now, when we suspend to RAM, the loaded microcode gets cleared so we > need to reload but there's no patch saved in the cache. > > Removing this optimization fixes this issue and all is fine and dandy. > > Signed-off-by: Borislav Petkov <bp@suse.de> So this one needs to go into x86/urgent Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 01/13] x86/microcode/intel: Drop stashed AP patch pointer optimization Borislav Petkov <bp@alien8.de> - 2017-01-17 18:50 +0100 Re: [PATCH 01/13] x86/microcode/intel: Drop stashed AP patch pointer optimization Thomas Gleixner <tglx@linutronix.de> - 2017-01-17 21:10 +0100
csiph-web