From: "Egger, Christoph" <chegger@amazon.de>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
Jan Beulich <JBeulich@suse.com>,
"Dong, Eddie" <eddie.dong@intel.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/3] Nested VMX: update nested paging mode when vmswitch is in progress
Date: Tue, 21 Jan 2014 10:46:05 +0100 [thread overview]
Message-ID: <52DE41DD.70502@amazon.de> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0A9C1688@SHSMSX104.ccr.corp.intel.com>
On 21.01.14 09:49, Zhang, Yang Z wrote:
> Egger, Christoph wrote on 2014-01-20:
>> On 14.01.14 08:38, Zhang, Yang Z wrote:
>>> Jan Beulich wrote on 2014-01-14:
>>>>>>> On 14.01.14 at 03:33, "Zhang, Yang Z" <yang.z.zhang@intel.com>
>> wrote:
>>>>> Zhang, Yang Z wrote on 2013-12-24:
>>>>>
>>>>> Any comments ?
>>>>
>>>> Considering Christoph's comments and reservations, if you can't
>>>> alone deal with this I think you should work with the AMD people to
>>>> eliminate or address his concerns.
>>>>
>>>
>>> Yes. But the problem puzzled me is that Christoph said nested SVM works
>>> well w/o my patch which I cannot understand. Because according my
>>> analysis in previous thread, it also buggy in AMD side. But if they
>>> really solved the issue in their side, I wonder how they fix it.
>>> Perhaps I can use the same solution in VMX side without touch the
>>> common code.
>>>
>>> Christoph, can you help to check it? thanks.
>>
>> The fix I mentioned solves the vmswitch problem on AMD side.
>
> But the current code is buggy with your fixing even in AMD side, see below scenario:
> virtual vmentry:
> Expected result: nested mode is being updated.
> Current result in SVM:
> !vcpu_in_guestmode and vmswitch_in_progress: L1's paging mode is updated. Wrong.
>
> I cannot understand why you said it is working.
This page mode problem you discovered that needs to be addressed for
both SVM and VMX.
The fix I am saying is working solves the problem of emulating an MMIO
instruction which is finished in the softirq while an interrupt
can cause a vmswitch during instruction emulation.
We are talking about two different issues. One is fixed on AMD side and
one not.
Christoph
next prev parent reply other threads:[~2014-01-21 10:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 2:06 [PATCH 0/3] some nested vmx fixing to hyper-v Yang Zhang
2013-12-12 2:06 ` [PATCH 1/3] Nested VMX: update nested paging mode when vmswitch is in progress Yang Zhang
2013-12-12 11:04 ` Egger, Christoph
2013-12-13 3:30 ` Zhang, Yang Z
2013-12-17 1:10 ` Zhang, Yang Z
2013-12-18 8:58 ` Dong, Eddie
2013-12-18 10:08 ` Jan Beulich
2013-12-18 10:24 ` Zhang, Yang Z
2013-12-18 12:05 ` Egger, Christoph
2013-12-23 1:34 ` Zhang, Yang Z
2013-12-24 11:35 ` Zhang, Yang Z
2014-01-14 2:33 ` Zhang, Yang Z
2014-01-14 7:29 ` Jan Beulich
2014-01-14 7:38 ` Zhang, Yang Z
2014-01-20 9:07 ` Egger, Christoph
2014-01-21 8:49 ` Zhang, Yang Z
2014-01-21 9:46 ` Egger, Christoph [this message]
2013-12-18 15:56 ` Dong, Eddie
2013-12-12 2:06 ` [PATCH 2/3] VMX, apicv: Set "NMI-window exiting" for NMI Yang Zhang
2014-01-08 1:23 ` Zhang, Yang Z
2014-01-08 1:28 ` Andrew Cooper
2014-01-08 1:36 ` Zhang, Yang Z
2014-01-08 1:41 ` Zhang, Yang Z
2013-12-12 2:06 ` [PATCH 3/3] Nested VMX: Setup the virtual NMI exiting info Yang Zhang
2013-12-18 9:00 ` Dong, Eddie
2013-12-18 5:39 ` [PATCH 0/3] some nested vmx fixing to hyper-v Zhang, Yang Z
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=52DE41DD.70502@amazon.de \
--to=chegger@amazon.de \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=xen-devel@lists.xenproject.org \
--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).