From: Pavel Fedin <p.fedin@samsung.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] Make KVM/MSI code device-ID-aware
Date: Tue, 13 Oct 2015 15:11:59 +0300 [thread overview]
Message-ID: <cover.1444737974.git.p.fedin@samsung.com> (raw)
This small series is actually an extraction from vITS support RFC
(https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg07074.html).
Nobody reviewed it so far, however some bits of it could actually be
applied early. This series consists only of those parts, which do not
depend on any new unreleased kernel APIs.
Pavel Fedin (3):
kvm: Make KVM_CAP_SIGNAL_MSI globally available
hw/pci: Introduce msi_device_id()
kvm: Pass PCI device pointer to MSI routing functions
hw/i386/kvm/pci-assign.c | 9 +++++----
hw/pci/msi.c | 2 +-
hw/vfio/pci.c | 11 ++++++-----
hw/virtio/virtio-pci.c | 5 +++--
include/hw/pci/msi.h | 5 +++++
include/sysemu/kvm.h | 14 ++++++++++++--
kvm-all.c | 15 ++++++++-------
kvm-stub.c | 5 +++--
8 files changed, 43 insertions(+), 23 deletions(-)
--
2.4.4
next reply other threads:[~2015-10-13 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 12:11 Pavel Fedin [this message]
2015-10-13 12:12 ` [Qemu-devel] [PATCH 1/3] kvm: Make KVM_CAP_SIGNAL_MSI globally available Pavel Fedin
2015-10-13 12:12 ` [Qemu-devel] [PATCH 2/3] hw/pci: Introduce msi_device_id() Pavel Fedin
2015-10-13 12:56 ` Michael S. Tsirkin
2015-10-13 13:24 ` Pavel Fedin
2015-10-13 12:12 ` [Qemu-devel] [PATCH 3/3] kvm: Pass PCI device pointer to MSI routing functions Pavel Fedin
2015-10-13 13:00 ` [Qemu-devel] [PATCH 0/3] Make KVM/MSI code device-ID-aware Michael S. Tsirkin
2015-10-13 13:49 ` Pavel Fedin
2015-10-13 14:03 ` Michael S. Tsirkin
2015-10-13 15:17 ` Pavel Fedin
2015-10-13 15:58 ` Michael S. Tsirkin
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=cover.1444737974.git.p.fedin@samsung.com \
--to=p.fedin@samsung.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).