All of lore.kernel.org
 help / color / mirror / Atom feed
From: "James (song wei)" <jsong@novell.com>
To: xen-devel@lists.xensource.com
Subject: Re: mce_wrmsr() and (at least) HVM guests
Date: Tue, 1 Dec 2009 22:18:12 -0800 (PST)	[thread overview]
Message-ID: <26604136.post@talk.nabble.com> (raw)
In-Reply-To: <4B1509BD0200007800022D3B@vpn.id2.novell.com>


Jan,

IMO, mce_wrmsr() shouldn't return -1 as a workaround, which leads to a #GP
in the
guest, at lease in MSR_IA32_MCG_CTL writting. Pnerhaps, it happens with
IOMMU ad the GART.

-James Song (wei)



Jan Beulich wrote:
> 
> With mce_wrmsr() not permitting to write other than all zeroes or all ones
> to MCG_CTL and MCn_CTL, it is not possible for guests to implement
> workarounds (see the one in mce_cpu_quirks() which has been present in
> Linux versions for a very long time). While one could expect PV guests to
> be aware of that (and avoid the workaround), HVM guests clearly can't
> be expected to. Thus the question is whether the handling should be
> made a little more permissive.
> 
> Initially I had thought of just making Xen check whether the bit(s) in
> question are also off in the physical MSR, but that would imply that
> Xen always has implemented at least all of the workarounds any guest
> may know of. I'm not sure I have a good other idea, short of allowing
> all writes to succeed.
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/mce_wrmsr%28%29-and-%28at-least%29-HVM-guests-tp26590226p26604136.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

  reply	other threads:[~2009-12-02  6:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 11:19 mce_wrmsr() and (at least) HVM guests Jan Beulich
2009-12-02  6:18 ` James (song wei) [this message]
2009-12-22 13:02 ` Jan Beulich
2009-12-23  3:22   ` Jiang, Yunhong
2010-01-04  8:09     ` Jan Beulich
2010-01-04  8:31       ` Jiang, Yunhong
2010-01-04  9:08         ` 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=26604136.post@talk.nabble.com \
    --to=jsong@novell.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.