From: Lan Tianyu <tianyu.lan@intel.com>
To: qemu-devel@nongnu.org, xen-devel@lists.xenproject.org
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: [RFC PATCH V2 0/2] Qemu: Add Xen vIOMMU interrupt remapping function.
Date: Thu, 18 May 2017 01:32:58 -0400 [thread overview]
Message-ID: <1495085580-10631-1-git-send-email-tianyu.lan@intel.com> (raw)
Change since V1:
1) Move create/destroy vIOMMU and query vIOMMU capabilities to tool stack.
2) Fix some code style issue.
This patchset is to deal with MSI interrupt remapping request when guest
updates MSI registers.
Repo:
https://github.com/lantianyu/qemu/tree/xen_viommu_rfc_v2
Chao Gao (2):
xen-pt: bind/unbind interrupt remapping format MSI
msi: Handle remappable format interrupt request
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 +-
xen-hvm-stub.c | 2 +-
xen-hvm.c | 7 +++++-
7 files changed, 54 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-05-18 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 5:32 Lan Tianyu [this message]
2017-05-18 5:32 ` [RFC PATCH V2 1/2] xen-pt: bind/unbind interrupt remapping format MSI Lan Tianyu
2017-05-19 11:16 ` Anthony PERARD
2017-05-19 12:04 ` Jan Beulich
2017-05-23 12:16 ` Lan Tianyu
2017-05-23 17:06 ` Anthony PERARD
2017-05-24 1:40 ` Lan Tianyu
2017-05-18 5:33 ` [RFC PATCH V2 2/2] msi: Handle remappable format interrupt request Lan Tianyu
2017-05-19 11:57 ` Anthony PERARD
2017-05-22 2:41 ` Lan Tianyu
2017-05-18 13:56 ` [Qemu-devel] [RFC PATCH V2 0/2] Qemu: Add Xen vIOMMU interrupt remapping function no-reply
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=1495085580-10631-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.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).