From: Feng Wu <feng.wu@intel.com>
To: xen-devel@lists.xen.org
Cc: Feng Wu <feng.wu@intel.com>
Subject: [PATCH v11 0/2] Add VT-d Posted-Interrupts support
Date: Thu, 28 Jan 2016 13:12:29 +0800 [thread overview]
Message-ID: <1453957951-17062-1-git-send-email-feng.wu@intel.com> (raw)
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in the following URL:
http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html
Feng Wu (2):
vmx: VT-d posted-interrupt core logic handling
Add a command line parameter for VT-d posted-interrupts
docs/misc/xen-command-line.markdown | 9 +-
xen/arch/x86/hvm/vmx/vmcs.c | 2 +
xen/arch/x86/hvm/vmx/vmx.c | 179 ++++++++++++++++++++++++++++++++++++
xen/common/schedule.c | 4 +
xen/drivers/passthrough/iommu.c | 3 +
xen/drivers/passthrough/vtd/iommu.c | 2 +
xen/include/asm-arm/domain.h | 2 +
xen/include/asm-x86/hvm/hvm.h | 5 +
xen/include/asm-x86/hvm/vmx/vmcs.h | 14 +++
xen/include/asm-x86/hvm/vmx/vmx.h | 4 +
10 files changed, 223 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2016-01-28 5:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 5:12 Feng Wu [this message]
2016-01-28 5:12 ` [PATCH v11 1/2] vmx: VT-d posted-interrupt core logic handling Feng Wu
2016-01-28 16:38 ` Jan Beulich
2016-01-29 1:53 ` Wu, Feng
2016-01-29 9:31 ` Jan Beulich
2016-02-02 4:48 ` Wu, Feng
2016-02-02 9:53 ` Jan Beulich
2016-02-16 6:33 ` Wu, Feng
2016-02-16 10:23 ` Jan Beulich
2016-02-10 12:25 ` George Dunlap
2016-02-16 5:54 ` Wu, Feng
2016-02-10 12:35 ` George Dunlap
2016-02-16 6:00 ` Wu, Feng
2016-01-28 5:12 ` [PATCH v11 2/2] Add a command line parameter for VT-d posted-interrupts Feng Wu
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=1453957951-17062-1-git-send-email-feng.wu@intel.com \
--to=feng.wu@intel.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).