From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: 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 17:25:01 +0100 [thread overview]
Message-ID: <CC52DD6D.3C261%keir.xen@gmail.com> (raw)
In-Reply-To: <502D34E00200007800095977@nat28.tlf.novell.com>
On 16/08/2012 16:58, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> On 16.08.12 at 17:28, Keir Fraser <keir@xen.org> wrote:
>> 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?
>
> Exactly those - they were kind enough to lend me a system. I'm
> having a patch queued for post-4.2 to enable VMX and a few
> other vendor specific things on them, but of course a prereq for
> testing this was that the system would boot at all under Xen.
Very cool! :-)
-- Keir
> Jan
>
prev parent reply other threads:[~2012-08-16 16:25 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
2012-08-16 15:58 ` Jan Beulich
2012-08-16 16:25 ` Keir Fraser [this message]
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=CC52DD6D.3C261%keir.xen@gmail.com \
--to=keir.xen@gmail.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).