From: Lan Tianyu <tianyu.lan@intel.com>
To: qemu-devel@nongnu.org, xen-devel@lists.xensource.com
Cc: Lan Tianyu <tianyu.lan@intel.com>,
kevin.tian@intel.com, sstabellini@kernel.org, mst@redhat.com,
marcel@redhat.com, anthony.perard@citrix.com, chao.gao@intel.com
Subject: [PATCH 0/3] Qemu: Add Xen vIOMMU interrupt remapping function support
Date: Thu, 29 Jun 2017 01:49:51 -0400 [thread overview]
Message-ID: <1498715394-16402-1-git-send-email-tianyu.lan@intel.com> (raw)
This patchset is to deal with MSI interrupt remapping request when guest
updates MSI registers.
Chao Gao (3):
i386/msi: Correct mask of destination ID in MSI address
xen-pt: bind/unbind interrupt remapping format MSI
msi: Handle remappable format interrupt request
configure | 54 +++++++++++++++++++++++++++++++++++++++++++
hw/pci/msi.c | 5 ++--
hw/pci/msix.c | 4 +++-
hw/xen/xen_pt_msi.c | 52 ++++++++++++++++++++++++++++++-----------
include/hw/i386/apic-msidef.h | 3 ++-
include/hw/xen/xen.h | 2 +-
include/hw/xen/xen_common.h | 25 ++++++++++++++++++++
xen-hvm-stub.c | 2 +-
xen-hvm.c | 8 ++++++-
9 files changed, 134 insertions(+), 21 deletions(-)
--
1.8.3.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-06-29 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 5:49 Lan Tianyu [this message]
2017-06-29 5:49 ` [PATCH 1/3] i386/msi: Correct mask of destination ID in MSI address Lan Tianyu
2017-06-30 13:49 ` Anthony PERARD
2017-07-04 2:31 ` [Qemu-devel] " Peter Xu
2017-06-29 5:49 ` [PATCH 2/3] xen-pt: bind/unbind interrupt remapping format MSI Lan Tianyu
2017-06-30 15:48 ` Anthony PERARD
2017-07-04 1:52 ` Lan Tianyu
2017-06-29 5:49 ` [PATCH 3/3] msi: Handle remappable format interrupt request Lan Tianyu
2017-06-30 15:52 ` Anthony PERARD
2017-07-06 23:50 ` [Qemu-devel] [PATCH 0/3] Qemu: Add Xen vIOMMU interrupt remapping function support no-reply
2017-07-07 0:02 ` Fam Zheng
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=1498715394-16402-1-git-send-email-tianyu.lan@intel.com \
--to=tianyu.lan@intel.com \
--cc=anthony.perard@citrix.com \
--cc=chao.gao@intel.com \
--cc=kevin.tian@intel.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.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).