From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/ucode: don't crash during AP bringup on non-Intel, non-AMD CPUs
Date: Thu, 16 Aug 2012 16:28:49 +0100 [thread overview]
Message-ID: <CC52D041.4973A%keir@xen.org> (raw)
In-Reply-To: <502D2C3A0200007800095918@nat28.tlf.novell.com>
On 16/08/2012 16:22, "Jan Beulich" <JBeulich@suse.com> wrote:
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Do we support any such processors? Newer VIA processors maybe?
Anyhow,
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/arch/x86/microcode.c
> +++ b/xen/arch/x86/microcode.c
> @@ -109,6 +109,9 @@ int microcode_resume_cpu(int cpu)
> struct cpu_signature nsig;
> unsigned int cpu2;
>
> + if ( !microcode_ops )
> + return 0;
> +
> spin_lock(µcode_mutex);
>
> err = microcode_ops->collect_cpu_info(cpu, &uci->cpu_sig);
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-08-16 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 15:22 [PATCH] x86/ucode: don't crash during AP bringup on non-Intel, non-AMD CPUs Jan Beulich
2012-08-16 15:28 ` Keir Fraser [this message]
2012-08-16 15:58 ` Jan Beulich
2012-08-16 16:25 ` Keir Fraser
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=CC52D041.4973A%keir@xen.org \
--to=keir@xen.org \
--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).