Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1664141 > unrolled thread

[PATCH 0/2] microcode: Do early microcode application during resume-from-RAM

Started byBorislav Petkov <bp@alien8.de>
First post2017-06-12 20:00 +0200
Last post2017-06-13 10:40 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM Borislav Petkov <bp@alien8.de> - 2017-06-12 20:00 +0200
    Re: [PATCH 0/2] microcode: Do early microcode application during  resume-from-RAM Henrique de Moraes Holschuh <hmh@hmh.eng.br> - 2017-06-12 20:30 +0200
    Re: [PATCH 0/2] microcode: Do early microcode application during  resume-from-RAM Dominik Brodowski <linux@dominikbrodowski.net> - 2017-06-13 08:00 +0200
      Re: [PATCH 0/2] microcode: Do early microcode application during  resume-from-RAM Borislav Petkov <bp@alien8.de> - 2017-06-13 10:40 +0200

#1664141 — [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM

FromBorislav Petkov <bp@alien8.de>
Date2017-06-12 20:00 +0200
Subject[PATCH 0/2] microcode: Do early microcode application during resume-from-RAM
Message-ID<tRBN7-5lx-3@gated-at.bofh.it>
From: Borislav Petkov <bp@suse.de>

Ok,

I think I've dreamt of a simple solution to the early microcode
application deal with suspend-to-RAM. The commit message of patch 2
should explain it in more detail. Patch 1 is a fix for 32-bit when the
ramdisk is being relocated.

I'm still testing but it seems to work.

Borislav Petkov (2):
  x86/microcode: Look for the initrd at the proper address on 32-bit
  x86/microcode/intel: Save pointer to ucode patch for early AP loading

 arch/x86/kernel/cpu/microcode/core.c  | 12 ++++++++++++
 arch/x86/kernel/cpu/microcode/intel.c | 25 +++++++++++++++++++++----
 2 files changed, 33 insertions(+), 4 deletions(-)

-- 
2.13.0

[toc] | [next] | [standalone]


#1664167 — Re: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM

FromHenrique de Moraes Holschuh <hmh@hmh.eng.br>
Date2017-06-12 20:30 +0200
SubjectRe: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM
Message-ID<tRCgb-5LZ-43@gated-at.bofh.it>
In reply to#1664141
On Mon, 12 Jun 2017, Borislav Petkov wrote:
> I think I've dreamt of a simple solution to the early microcode
> application deal with suspend-to-RAM. The commit message of patch 2
> should explain it in more detail. Patch 1 is a fix for 32-bit when the
> ramdisk is being relocated.
> 
> I'm still testing but it seems to work.

And it ended up being really simple, too.  Thank you very much,
Borislav!

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]


#1664458 — Re: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM

FromDominik Brodowski <linux@dominikbrodowski.net>
Date2017-06-13 08:00 +0200
SubjectRe: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM
Message-ID<tRN1V-41I-15@gated-at.bofh.it>
In reply to#1664141
Boris,

On Mon, Jun 12, 2017 at 07:58:52PM +0200, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
> 
> Ok,
> 
> I think I've dreamt of a simple solution to the early microcode
> application deal with suspend-to-RAM. The commit message of patch 2
> should explain it in more detail. Patch 1 is a fix for 32-bit when the
> ramdisk is being relocated.
> 
> I'm still testing but it seems to work.

Nice job; works fine here.

Best,
	Dominik

[toc] | [prev] | [next] | [standalone]


#1664593 — Re: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM

FromBorislav Petkov <bp@alien8.de>
Date2017-06-13 10:40 +0200
SubjectRe: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM
Message-ID<tRPwJ-5EB-1@gated-at.bofh.it>
In reply to#1664458
On Tue, Jun 13, 2017 at 07:55:34AM +0200, Dominik Brodowski wrote:
> Nice job; works fine here.

Thanks for testing, I'll add your Tested-by.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web