From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Eddie Dong <eddie.dong@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH] VMX: Eliminate cr3 store/load vmexit when UG enabled
Date: Mon, 28 Oct 2013 13:52:08 +0000 [thread overview]
Message-ID: <526E6C08.9020704@citrix.com> (raw)
In-Reply-To: <526E732E02000078000FD475@nat28.tlf.novell.com>
On 28/10/13 13:22, Jan Beulich wrote:
>>>> On 24.10.13 at 06:41, "Zhang, Yang Z" <yang.z.zhang@intel.com> wrote:
>> Andrew Cooper wrote on 2013-10-23:
>>> On 23/10/13 08:39, Yang Zhang wrote:
>>>> From: Yang Zhang <yang.z.zhang@Intel.com>
>>>>
>>>> With the feature of unrestricted guest, there should no vmexit be
>>>> triggered when guest accesses the cr3 in non-paging mode.
>>>>
>>>> Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com>
>>> You English here confused me for a bit. I presume you mean "Xen
>>> should not cause vmexits for cr3 accesses in unrestricted guests",
>>> whereas the current meaning implies that hardware wont generate a
>>> vmexit for cr3 accesses for unrestricted guests (which is not correct
>> according to the SDM).
>> Apology for my poor English. Yes, your understanding is right.
> So assuming we'll get an ack from one of the VMX maintainers,
> should this then be committed with the suggested change to the
> description? Also, Andrew, any more concerns regarding this
> change (IOW did Yang address your earlier questions)?
>
> Jan
>
I think so, but I really don't think I know the implications of the
changes well enough to be happy giving it a Reviewed-by tag.
Given the clarification regarding the commit message, I shall defer to
the maintainers for the correctness of the change.
~Andrew
next prev parent reply other threads:[~2013-10-28 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 7:39 [PATCH] VMX: Eliminate cr3 store/load vmexit when UG enabled Yang Zhang
2013-10-23 14:40 ` Andrew Cooper
2013-10-24 4:41 ` Zhang, Yang Z
2013-10-28 13:22 ` Jan Beulich
2013-10-28 13:52 ` Andrew Cooper [this message]
2013-10-29 1:09 ` Zhang, Yang Z
2013-10-29 1:49 ` Nakajima, Jun
2013-10-29 1:02 ` Zhang, Yang Z
2013-10-29 7:42 ` 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=526E6C08.9020704@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@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 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).