From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] xen/vPMU: Do not clobber IA32_MISC_ENABLE
Date: Mon, 7 Mar 2016 09:45:50 -0500 [thread overview]
Message-ID: <56DD941E.2000008@oracle.com> (raw)
In-Reply-To: <1457360841-28587-1-git-send-email-andrew.cooper3@citrix.com>
On 03/07/2016 09:27 AM, Andrew Cooper wrote:
> The VMX RDMSR intercept for MSR_IA32_MISC_ENABLE falls through into
> vpmu_do_rdmsr(), so that core2_vpmu_do_rdmsr() may play with the PTS and PEBS
> UNAVAIL bits.
>
> Some 64bit Windows include IA32_MISC_ENABLE in the set of items checked by
> PatchGuard, and will suffer a BSOD 0x109 CRITICAL_STRUCTURE_CORRUPTION if the
> contents change on migrate.
>
> The vPMU infrastructure should not clobber IA32_MISC_ENABLE at all.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>
> This appears to have been broken since the vPMU code was first introduced. It
> appears to have lurked this log due to a hole (now fixed) in XenServers
> upgrade testing. The BSODs occur ~80% of the time on Win 8 thru 10, but
> appear very hard to provoke on Windows 7.
>
> This MSR still leaks mostly host state through into the guest. Therefore
> migration of windows is still liable to crash if moving between two
> non-identical servers. I need to get proper MSR levelling sorted before this
> issue can be resolved fully.
> ---
> xen/arch/x86/cpu/vpmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/arch/x86/cpu/vpmu.c b/xen/arch/x86/cpu/vpmu.c
> index 237b5ff..2f9ddf6 100644
> --- a/xen/arch/x86/cpu/vpmu.c
> +++ b/xen/arch/x86/cpu/vpmu.c
> @@ -169,7 +169,7 @@ int vpmu_do_msr(unsigned int msr, uint64_t *msr_content,
> return ret;
>
> nop:
> - if ( !is_write )
> + if ( !is_write && (msr != MSR_IA32_MISC_ENABLE) )
> *msr_content = 0;
>
> return 0;
This is Intel-specific register so the test should really be happening
in vpmu_intel.c. Of course then you'd need to always dereference
vcpu_vpmu() and possibly add more checks to read/write ops (to mirror
the one at the top of vpmu_do_msr()).
So maybe at least have the vendor check too??
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-07 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 14:27 [PATCH] xen/vPMU: Do not clobber IA32_MISC_ENABLE Andrew Cooper
2016-03-07 14:45 ` Boris Ostrovsky [this message]
2016-03-07 14:58 ` Andrew Cooper
2016-03-07 15:11 ` Boris Ostrovsky
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=56DD941E.2000008@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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).