From: Christoph Egger <Christoph.Egger@amd.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Dong, Eddie" <eddie.dong@intel.com>
Subject: Re: RFC: Nested VMX patch series 00
Date: Wed, 1 Jun 2011 12:34:33 +0200 [thread overview]
Message-ID: <4DE615B9.2090609@amd.com> (raw)
In-Reply-To: <20110601101559.GF5098@whitby.uk.xensource.com>
On 06/01/11 12:15, Tim Deegan wrote:
> At 11:56 +0200 on 01 Jun (1306929406), Christoph Egger wrote:
>> On 06/01/11 06:11, Dong, Eddie wrote:
>>> Keir/Tim:
>>> Here is the nested VMX support series for comments.
>>> The current solution works with host shadow page table. The virtual EPT
>>> support will come soon.
>>
>> I am surprised that shadow-on-shadow works w/o touching anything in
>> xen/arch/x86/mm/*
>
> What do you think should break? One major thing was that we didn't
> properly report invalid PTE bits, but that's been fixed.
I thought some code to switch forth and back between two shadow page
tables needs to be added at least (one to run l1 guest and one to run
l2 guest).
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-06-01 10:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 2:14 [xen-4.1-testing test] 7468: tolerable FAIL - PUSHED xen.org
2011-06-01 3:44 ` pre-cleanup1 for nested VMX Dong, Eddie
2011-06-01 3:47 ` pre-cleanup2 " Dong, Eddie
2011-06-01 3:49 ` RFC: Nested VMX patch series 01: data structure Dong, Eddie
2011-06-01 3:51 ` RFC: Nested VMX patch series 02: wrap APIs Dong, Eddie
2011-06-01 9:13 ` Christoph Egger
2011-06-01 3:52 ` RFC: Nested VMX patch series 03: vmxon_off Dong, Eddie
2011-06-01 3:55 ` RFC: Nested VMX patch series 04: virtual VMCS structure and APIs Dong, Eddie
2011-06-01 3:57 ` RFC: Nested VMX patch series 05: vmptrld Dong, Eddie
2011-06-01 3:57 ` RFC: Nested VMX patch series 05: vmptrst Dong, Eddie
2011-06-01 3:58 ` RFC: Nested VMX patch series 07: vmclear Dong, Eddie
2011-06-01 3:59 ` RFC: Nested VMX patch series 08: vmwrite Dong, Eddie
2011-06-01 4:00 ` RFC: Nested VMX patch series 09: vmread Dong, Eddie
2011-06-01 4:01 ` RFC: Nested VMX patch series 10: vmcs switching API Dong, Eddie
2011-06-01 4:02 ` RFC: Nested VMX patch series 11: vmresume Dong, Eddie
2011-06-01 4:03 ` RFC: Nested VMX patch series 12: shadow vmcs control Dong, Eddie
2011-06-01 4:04 ` RFC: Nested VMX patch series 12: real VMCS switch Dong, Eddie
2011-06-01 4:05 ` RFC: Nested VMX patch series 14: exceptions Dong, Eddie
2011-06-01 4:06 ` RFC: Nested VMX patch series 15: exit from n2 guest Dong, Eddie
2011-06-01 4:07 ` RFC: Nested VMX patch series 16: fpu Dong, Eddie
2011-06-01 4:08 ` RFC: Nested VMX patch series 17: cr4 Dong, Eddie
2011-06-01 4:09 ` RFC: Nested VMX patch series 18: capability Dong, Eddie
2011-06-01 4:11 ` RFC: Nested VMX patch series 00 Dong, Eddie
2011-06-01 8:47 ` Ian Campbell
2011-06-01 9:50 ` Tim Deegan
2011-06-01 9:56 ` Christoph Egger
2011-06-01 10:15 ` Tim Deegan
2011-06-01 10:34 ` Christoph Egger [this message]
2011-06-01 10:39 ` Tim Deegan
2011-06-01 23:28 ` Dong, Eddie
2011-06-02 5:02 ` Tian, Kevin
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=4DE615B9.2090609@amd.com \
--to=christoph.egger@amd.com \
--cc=Tim.Deegan@citrix.com \
--cc=eddie.dong@intel.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 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).