From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: "Kevin Tian" <kevin.tian@intel.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Jun Nakajima" <jun.nakajima@intel.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH 0/6] x86/vmx: Misc fixes and improvements
Date: Mon, 28 May 2018 15:27:52 +0100 [thread overview]
Message-ID: <1527517678-1779-1-git-send-email-andrew.cooper3@citrix.com> (raw)
Patch 1 might want to be considered for 4.11. All others are 4.12 material at
this point.
Andrew Cooper (6):
x86/vmx: Fix handing of MSR_DEBUGCTL on VMExit
x86: Improvements to ler debugging
x86/pat: Simplify host PAT handling
x86/vmx: Simplify PAT handling during vcpu construction
x86/vmx: Defer vmx_vmcs_exit() as long as possible in construct_vmcs()
x86/vmx: Drop VMX signal for full real-mode
docs/misc/xen-command-line.markdown | 6 ++++
xen/arch/x86/acpi/suspend.c | 3 +-
xen/arch/x86/cpu/common.c | 9 +-----
xen/arch/x86/hvm/mtrr.c | 2 +-
xen/arch/x86/hvm/vmx/entry.S | 9 ++++++
xen/arch/x86/hvm/vmx/vmcs.c | 22 +++++---------
xen/arch/x86/hvm/vmx/vmx.c | 14 ++-------
xen/arch/x86/traps.c | 58 ++++++++++++++++++-------------------
xen/arch/x86/x86_64/traps.c | 14 ++++++---
xen/include/asm-x86/cpufeature.h | 2 +-
xen/include/asm-x86/cpufeatures.h | 1 +
xen/include/asm-x86/msr.h | 2 +-
xen/include/asm-x86/processor.h | 7 ++++-
xen/include/asm-x86/x86_64/page.h | 8 +++++
14 files changed, 83 insertions(+), 74 deletions(-)
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-05-28 14:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 14:27 Andrew Cooper [this message]
2018-05-28 14:27 ` [PATCH 1/6] x86/vmx: Fix handing of MSR_DEBUGCTL on VMExit Andrew Cooper
2018-05-29 10:33 ` Jan Beulich
2018-05-29 18:08 ` Andrew Cooper
2018-05-30 7:32 ` Jan Beulich
2018-05-30 10:28 ` Andrew Cooper
2018-05-30 10:49 ` Jan Beulich
2018-05-30 17:34 ` [PATCH v2 " Andrew Cooper
2018-06-01 9:28 ` Jan Beulich
2018-06-05 7:54 ` Tian, Kevin
2018-05-28 14:27 ` [PATCH 2/6] x86: Improvements to ler debugging Andrew Cooper
2018-05-29 11:39 ` Jan Beulich
2018-05-29 18:09 ` Andrew Cooper
2018-06-05 7:55 ` Tian, Kevin
2018-05-28 14:27 ` [PATCH 3/6] x86/pat: Simplify host PAT handling Andrew Cooper
2018-05-29 11:40 ` Jan Beulich
2018-06-06 9:39 ` Roger Pau Monné
2018-05-28 14:27 ` [PATCH 4/6] x86/vmx: Simplify PAT handling during vcpu construction Andrew Cooper
2018-05-29 11:41 ` Jan Beulich
2018-06-05 7:57 ` Tian, Kevin
2018-06-06 9:42 ` Roger Pau Monné
2018-05-28 14:27 ` [PATCH 5/6] x86/vmx: Defer vmx_vmcs_exit() as long as possible in construct_vmcs() Andrew Cooper
2018-05-29 11:43 ` Jan Beulich
2018-06-05 8:00 ` Tian, Kevin
2018-06-06 9:45 ` Roger Pau Monné
2018-06-06 10:11 ` Andrew Cooper
2018-05-28 14:27 ` [PATCH 6/6] x86/vmx: Drop VMX signal for full real-mode Andrew Cooper
2018-06-05 8:01 ` Tian, Kevin
2018-06-06 10:03 ` Roger Pau Monné
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=1527517678-1779-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).