From: Borislav Petkov <bp@alien8.de>
To: Dominik Brodowski <linux@dominikbrodowski.net>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM
Date: Mon, 12 Jun 2017 19:58:52 +0200 [thread overview]
Message-ID: <20170612175854.14196-1-bp@alien8.de> (raw)
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
next reply other threads:[~2017-06-12 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 17:58 Borislav Petkov [this message]
2017-06-12 17:58 ` [PATCH 1/2] x86/microcode: Look for the initrd at the proper address on 32-bit Borislav Petkov
2017-06-12 17:58 ` [PATCH 2/2] x86/microcode/intel: Save pointer to ucode patch for early AP loading Borislav Petkov
2017-06-12 18:26 ` [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM Henrique de Moraes Holschuh
2017-06-13 5:55 ` Dominik Brodowski
2017-06-13 8:29 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170612175854.14196-1-bp@alien8.de \
--to=bp@alien8.de \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox