From: Chao Gao <chao.gao@intel.com>
To: qemu-devel@nongnu.org
Cc: Chao Gao <chao.gao@intel.com>,
Anthony Perard <anthony.perard@citrix.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: [Qemu-devel] [PATCH v3 0/3] Qemu: add Xen vIOMMU interrupt remapping function support
Date: Fri, 17 Nov 2017 14:24:22 +0800 [thread overview]
Message-ID: <1510899865-40323-1-git-send-email-chao.gao@intel.com> (raw)
This patchset is to deal with MSI interrupt remapping request when guest
updates MSI registers.
In case of conflicts, this series also can be found in my personal github:
Xen: https://github.com/gc1008/viommu_xen.git vIOMMU4
Qemu: https://github.com/gc1008/viommu_qemu.git vIOMMU3
Any comments would be highly appreciated. And below is the change histroy
Changes from v2:
In last version, a new interface is used for binding a guest remappable msi
with a physical interrupt, while the old interface is used for binding
non-remappable msi. But for AMD, only from the MSI message itself, the
interrupt format cannot be infered. To address this, we decide to pass the
whole guest msi message to Xen and let vIOMMUs in Xen detemine whether
an given interrupt is remappable or not.
So the following changes are made:
- Instead of introducing a new interface for binding remapping format msi,
the exist interface is modified to support msi of both format.
- In patch 3, define MSI_ADDR_IF_MASK inside a function because
it is intel-specific. It is improper to define it in a common header.
Chao Gao (3):
i386/msi: Correct mask of destination ID in MSI address
xen/pt: Pass the whole msi addr/data to Xen
msi: Handle remappable format interrupt request
hw/i386/xen/xen-hvm.c | 10 ++++++++-
hw/pci/msi.c | 5 +++--
hw/pci/msix.c | 4 +++-
hw/xen/xen_pt_msi.c | 49 ++++++++++++-------------------------------
include/hw/i386/apic-msidef.h | 2 +-
include/hw/xen/xen.h | 2 +-
stubs/xen-hvm.c | 2 +-
7 files changed, 31 insertions(+), 43 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-11-17 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 6:24 Chao Gao [this message]
2017-11-17 6:24 ` [Qemu-devel] [PATCH v3 1/3] i386/msi: Correct mask of destination ID in MSI address Chao Gao
2017-11-17 13:24 ` Michael S. Tsirkin
2017-11-20 7:56 ` Chao Gao
2017-11-17 6:24 ` [Qemu-devel] [PATCH v3 2/3] xen/pt: Pass the whole msi addr/data to Xen Chao Gao
2017-12-11 17:59 ` Anthony PERARD
2017-12-11 18:28 ` Chao Gao
2017-11-17 6:24 ` [Qemu-devel] [PATCH v3 3/3] msi: Handle remappable format interrupt request Chao Gao
2017-12-11 18:07 ` Anthony PERARD
2017-12-11 18:35 ` Chao Gao
2017-11-17 6:58 ` [Qemu-devel] [PATCH v3 0/3] Qemu: add Xen vIOMMU interrupt remapping function support 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=1510899865-40323-1-git-send-email-chao.gao@intel.com \
--to=chao.gao@intel.com \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).