From: "Jan Beulich" <jbeulich@novell.com>
To: Xin B Li <xin.b.li@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: VMX: emulated guest use SYSENTER MSRs
Date: Mon, 09 Jul 2007 10:05:35 +0100 [thread overview]
Message-ID: <4692167F.76E4.0078.0@novell.com> (raw)
In-Reply-To: <B30DA1341B0CFA4893EF8A36B40B5C5D0159F9C8@pdsmsx411.ccr.corp.intel.com>
>>> "Li, Xin B" <xin.b.li@intel.com> 07.07.07 10:57 >>>
>I will send out the patch soon.
Not strictly necessary - I have this as part of a larger patch already. But if you
beat me in getting this out, I'll sync up with yours.
Jan
>-----Original Message-----
>From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
>Sent: Saturday, July 07, 2007 4:52 PM
>To: Li, Xin B; Jan Beulich; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] VMX: emulated guest use SYSENTER MSRs
>
>Since they are included in the VMCS, and read from there on
>save/restore,
>the vmexit appears to be unnecessary.
>
> -- Keir
>
>On 7/7/07 08:48, "Li, Xin B" <xin.b.li@intel.com> wrote:
>
>>
>>> What is the reason for not simply clearing the MSR bitmap bits
>>> for these three MSRs, and rather handling the reads/writes
>in software?
>>
>> I haven't checked those MSRs, the original concern is we need
>> save/restore them when context switch, is this needed?
>>
>> -Xin
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2007-07-09 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 12:41 VMX: emulated guest use SYSENTER MSRs Jan Beulich
2007-07-06 12:52 ` Keir Fraser
2007-07-07 7:48 ` Li, Xin B
2007-07-07 8:52 ` Keir Fraser
2007-07-07 8:57 ` Li, Xin B
2007-07-09 9:05 ` 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=4692167F.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.b.li@intel.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.