From: Boris Ostrovsky <boris.ostrovsky@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian.Campbell@citrix.com, Christoph_Egger@gmx.de, xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/ucode: Improve error handling and container file processing on AMD
Date: Fri, 7 Dec 2012 10:25:33 -0500 [thread overview]
Message-ID: <50C20A6D.3010803@amd.com> (raw)
In-Reply-To: <50C2147C02000078000AEFCC@nat28.tlf.novell.com>
On 12/07/2012 10:08 AM, Jan Beulich wrote:
>>>> On 07.12.12 at 14:46, Boris Ostrovsky <boris.ostrovsky@amd.com> wrote:
>> Do we really need what microcode_init() does?
>
> Oh yes, absolutely. How else would boot time microcode loading
> work for secondary CPUs without this? Note that the notifier only
> deals with the CPU_DEAD case.
start_secondary() -> microcode_resume_cpu() ->
microcode_ops->apply_microcode() will update non-boot CPUs in most cases.
This won't quite work when secondary CPU is different from (or at
different patch level than) boot CPU but that can be fixed.
-boris
next prev parent reply other threads:[~2012-12-07 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 18:28 [PATCH] x86/ucode: Improve error handling and container file processing on AMD Boris Ostrovsky
2012-12-07 10:21 ` Ian Campbell
2012-12-07 11:41 ` Jan Beulich
2012-12-07 13:46 ` Boris Ostrovsky
2012-12-07 15:08 ` Jan Beulich
2012-12-07 15:25 ` Boris Ostrovsky [this message]
2012-12-07 15:42 ` Jan Beulich
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=50C20A6D.3010803@amd.com \
--to=boris.ostrovsky@amd.com \
--cc=Christoph_Egger@gmx.de \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).