From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH v2 0/2] vmx/hap: optimize CR4 trapping
Date: Fri, 16 Feb 2018 12:10:27 +0000 [thread overview]
Message-ID: <20180216121029.6872-1-roger.pau@citrix.com> (raw)
Hello,
Following two-patch series optimize CR4 access for vmx/hap.
I couldn't figure out a similar approach for AMD, since according to
section 15.9 (Instruction Intercepts), you either intercept all access
to CR4 or none. In any case a similar optimization for AMD can always be
added later.
Thanks, Roger.
Roger Pau Monne (2):
x86/hvm: introduce cr_mask to store trapped bits of CR accesses
vmx/hap: optimize CR4 trapping
xen/arch/x86/hvm/svm/vmcb.c | 1 +
xen/arch/x86/hvm/vmx/vmcs.c | 1 +
xen/arch/x86/hvm/vmx/vmx.c | 39 +++++++++++++++++++++++++++++++++++++++
xen/arch/x86/hvm/vmx/vvmx.c | 2 ++
xen/arch/x86/monitor.c | 5 +++--
xen/include/asm-x86/hvm/vcpu.h | 3 +++
6 files changed, 49 insertions(+), 2 deletions(-)
--
2.16.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-02-16 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 12:10 Roger Pau Monne [this message]
2018-02-16 12:10 ` [PATCH v2 1/2] x86/hvm: introduce cr_mask to store trapped bits of CR accesses Roger Pau Monne
2018-02-16 12:49 ` Andrew Cooper
2018-02-19 15:04 ` Roger Pau Monné
2018-02-19 15:07 ` Andrew Cooper
2018-02-16 12:10 ` [PATCH v2 2/2] vmx/hap: optimize CR4 trapping Roger Pau Monne
2018-02-16 12:30 ` Razvan Cojocaru
2018-02-16 12:37 ` Roger Pau Monné
2018-02-16 12:39 ` Razvan Cojocaru
2018-02-16 15:03 ` Razvan Cojocaru
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=20180216121029.6872-1-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).