From: Joerg Roedel <joro@8bytes.org>
To: Dongxiao Xu <dongxiao.xu@intel.com>
Cc: jun.nakajima@intel.com, xen-devel@lists.xensource.com,
eddie.dong@intel.com, xiantao.zhang@intel.com, JBeulich@suse.com
Subject: Re: [PATCH v5 rebased 0/4] nested vmx: enable VMCS shadowing feature
Date: Tue, 29 Jan 2013 11:19:12 +0100 [thread overview]
Message-ID: <20130129101912.GB25591@8bytes.org> (raw)
In-Reply-To: <1358951532-20302-1-git-send-email-dongxiao.xu@intel.com>
Hi Dongxiao,
On Wed, Jan 23, 2013 at 10:32:08PM +0800, Dongxiao Xu wrote:
> The main purpose of this feature is to reduce or eliminate the number of VM exit
> for non-root VMREAD and VMWRITE. It provides the capability to link a
> "virtual VMCS" with the current running VMCS, so that after VM entry, the
> non-root VMREAD and VMWRITE can get/set related data directly from/to the
> "virtual VMCS" without trap and emulation.
This looks like a neat feature. I am wondering when I can use it. Is it
planned for Haswell or a later chip?
Thanks,
Joerg
prev parent reply other threads:[~2013-01-29 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 14:32 [PATCH v5 rebased 0/4] nested vmx: enable VMCS shadowing feature Dongxiao Xu
2013-01-23 14:32 ` [PATCH v5 rebased 1/4] nested vmx: Use a list to store the launched vvmcs for L1 VMM Dongxiao Xu
2013-01-25 2:13 ` Dong, Eddie
2013-01-23 14:32 ` [PATCH v5 rebased 2/4] nested vmx: use VMREAD/VMWRITE to construct vVMCS if enabled VMCS shadowing Dongxiao Xu
2013-01-25 2:26 ` Dong, Eddie
2013-01-23 14:32 ` [PATCH v5 rebased 3/4] nested vmx: optimize for bulk access of virtual VMCS Dongxiao Xu
2013-01-25 2:27 ` Dong, Eddie
2013-01-23 14:32 ` [PATCH v5 rebased 4/4] nested vmx: enable VMCS shadowing feature Dongxiao Xu
2013-01-23 14:55 ` Nakajima, Jun
2013-01-25 2:28 ` Dong, Eddie
2013-01-29 10:19 ` Joerg Roedel [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=20130129101912.GB25591@8bytes.org \
--to=joro@8bytes.org \
--cc=JBeulich@suse.com \
--cc=dongxiao.xu@intel.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.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).