From: "Egger, Christoph" <chegger@amazon.de>
To: Yang Zhang <yang.z.zhang@intel.com>, xen-devel@lists.xen.org
Cc: eddie.dong@intel.com, xiantao.zhang@intel.com, JBeulich@suse.com
Subject: Re: [PATCH 1/2] Nested VMX: update nested paging mode on vmexit
Date: Wed, 12 Feb 2014 10:22:05 +0100 [thread overview]
Message-ID: <52FB3D3D.9070909@amazon.de> (raw)
In-Reply-To: <1392170936-31362-1-git-send-email-yang.z.zhang@intel.com>
On 12.02.14 03:08, Yang Zhang wrote:
> From: Yang Zhang <yang.z.zhang@Intel.com>
>
> Since SVM and VMX use different mechanism to emulate the virtual-vmentry
> and virtual-vmexit, it's hard to update the nested paging mode correctly in
> common code. So we need to update the nested paging mode in their respective
> code path.
> SVM already updates the nested paging mode on vmexit. This patch adds the same
> logic in VMX side.
>
> Previous discussion is here:
> http://lists.xen.org/archives/html/xen-devel/2013-12/msg01759.html
>
> Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com>
Reviewed-by: Christoph Egger <chegger@amazon.de>
> ---
> xen/arch/x86/hvm/vmx/vmx.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
> index f6409d6..baf3040 100644
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -2541,6 +2541,7 @@ void vmx_vmexit_handler(struct cpu_user_regs *regs)
> vcpu_nestedhvm(v).nv_vmswitch_in_progress = 0;
> if ( nestedhvm_vcpu_in_guestmode(v) )
> {
> + paging_update_nestedmode(v);
> if ( nvmx_n2_vmexit_handler(regs, exit_reason) )
> goto out;
> }
>
prev parent reply other threads:[~2014-02-12 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 2:08 [PATCH 1/2] Nested VMX: update nested paging mode on vmexit Yang Zhang
2014-02-12 2:08 ` [PATCH 2/2] Nested EPT: fixing issue of translate L2 gva to L1 gfn Yang Zhang
2014-02-12 9:28 ` Egger, Christoph
2014-02-13 4:24 ` Zhang, Yang Z
2014-02-12 9:22 ` Egger, Christoph [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=52FB3D3D.9070909@amazon.de \
--to=chegger@amazon.de \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@intel.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).