From: "Jan Beulich" <JBeulich@novell.com>
To: Wei Huang2 <Wei.Huang2@amd.com>, Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Hans Rosenfeld <Hans.Rosenfeld@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen
Date: Mon, 05 Jul 2010 15:54:49 +0100 [thread overview]
Message-ID: <4C320E5902000078000098D6@vpn.id2.novell.com> (raw)
In-Reply-To: <EE335F95F28A664DB4A21289D2AA053B42E7D16D@SAUSEXMBP01.amd.com>
>>> On 05.07.10 at 16:23, "Huang2, Wei" <Wei.Huang2@amd.com> wrote:
> My thought was that this patch won't affect newer families of CPUs (i.e.
> production parts). I expected this erratum will be fixed on them. But if you
If you know that's going to be the case, then I agree.
> disagree, I will ask Keir to apply it to Xen 4.0.1.
Jan
prev parent reply other threads:[~2010-07-05 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 19:17 [PATCH] AMD OSVW (OS Visible Workaround) for Xen Wei Huang
2010-07-02 18:05 ` Keir Fraser
2010-07-02 18:57 ` Wei Huang
2010-07-05 7:11 ` Jan Beulich
2010-07-05 14:23 ` Huang2, Wei
2010-07-05 14:54 ` Jan Beulich [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=4C320E5902000078000098D6@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Hans.Rosenfeld@amd.com \
--cc=Wei.Huang2@amd.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).