All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Huang <wei.huang2@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "Rosenfeld, Hans" <Hans.Rosenfeld@amd.com>,
	"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen
Date: Fri, 2 Jul 2010 13:57:50 -0500	[thread overview]
Message-ID: <4C2E36AE.5060607@amd.com> (raw)
In-Reply-To: <C853E909.19508%keir.fraser@eu.citrix.com>

Thanks very much. I don't think 4.0.1 needs this patch.

-Wei

Keir Fraser wrote:
> On 01/07/2010 20:17, "Wei Huang" <wei.huang2@amd.com> wrote:
>
>   
>> This path enables AMD OSVW (OS Visible Workaround) feature for Xen. New
>> AMD errata will have a OSVW id assigned in the future. OS is supposed to
>> check OSVW status MSR to find out whether CPU has a specific erratum.
>> Legacy errata are also supported in this patch: traditional
>> family/model/stepping approach will be used if OSVW feature isn't
>> applicable.  This patch is adapted from Hans Rosenfeld's patch submitted
>> to Linux kernel .
>>     
>
> Applied to xen-unstable. Is this for 4.0.1 also? It is a big patch and it
> doesn't say it actually fixes any issues...
>
>  -- Keir
>
>   
>> Signed-off-by: Wei Huang <wei.huang2@amd.com>
>> Signed-off-by: Hans Rosenfeld <hands.rosenfeld@amd.com>
>> Acked-by: Jan Beulich <jbeulich@novell.com>
>>
>>     
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>   

  reply	other threads:[~2010-07-02 18:57 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 [this message]
2010-07-05  7:11     ` Jan Beulich
2010-07-05 14:23       ` Huang2, Wei
2010-07-05 14:54         ` 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=4C2E36AE.5060607@amd.com \
    --to=wei.huang2@amd.com \
    --cc=Hans.Rosenfeld@amd.com \
    --cc=JBeulich@novell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.