From: Jacob Shin <jacob.shin@amd.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yinghai@kernel.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Borislav Petkov <bp@alien8.de>,
Andreas Herrmann <herrmann.der.user@googlemail.com>,
<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
Jacob Shin <jacob.shin@amd.com>
Subject: [PATCH V2 0/2] x86/microcode/amd: early loading fixes
Date: Thu, 6 Jun 2013 14:45:49 -0500 [thread overview]
Message-ID: <1370547951-2701-1-git-send-email-jacob.shin@amd.com> (raw)
This patchset addreses two problems with early loading on AMD.
First, feedback from Yinghai that find_ucode_in_initrd() should be
marked __init:
https://lkml.org/lkml/2013/6/4/695
And second, feedback from Henrique that Intel early loading supports
multiple microcode firmware concatenated together, whereas the current
AMD implementation lacks this support:
https://lkml.org/lkml/2013/5/31/4
V2:
* test for !initrd_start before using it
* use __pa() instead of __pa_nodebug() on AP load
* fixed calculation of start offset and size of the microcode container file
Jacob Shin (2):
x86/microcode/amd: make find_ucode_in_initrd() __init
x86/microcode/amd: allow multiple families' bin files appended
together
arch/x86/kernel/microcode_amd_early.c | 176 +++++++++++++++++++++++++--------
1 file changed, 133 insertions(+), 43 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-06-06 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 19:45 Jacob Shin [this message]
2013-06-06 19:45 ` [PATCH V2 1/2] x86/microcode/amd: make find_ucode_in_initrd() __init Jacob Shin
2013-06-06 20:08 ` Yinghai Lu
2013-06-06 20:11 ` H. Peter Anvin
2013-06-06 19:45 ` [PATCH V2 2/2] x86/microcode/amd: allow multiple families' bin files appended together Jacob Shin
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=1370547951-2701-1-git-send-email-jacob.shin@amd.com \
--to=jacob.shin@amd.com \
--cc=bp@alien8.de \
--cc=herrmann.der.user@googlemail.com \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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
all inboxes | Powered by JetHome®