From: David Kiarie <davidkiarie4@gmail.com>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com, valentine.sinitsyn@gmail.com,
mst@redhat.com, pbonzini@redhat.com, ehabkost@redhat.com,
peter.maydell@linaro.org, David Kiarie <davidkiarie4@gmail.com>
Subject: [Qemu-devel] [RFC 0/2] Explicit SID for IOAPIC
Date: Tue, 9 Aug 2016 17:32:15 +0300 [thread overview]
Message-ID: <1470753137-18354-1-git-send-email-davidkiarie4@gmail.com> (raw)
IOMMU require platform device like IOAPIC and possibly HPET to make
interrupt requests using explicit SIDs which the currently don't.
This patches modify x86 code such that an MSIroute entry is affiliated with
a requester ID and, if present, a PCI device. This change doesn't seem
have any side effects as far as I can tell.
David Kiarie (2):
hw/msi: Allow platform devices to use explicit SID
hw/i386: enforce SID verification
hw/i386/intel_iommu.c | 82 ++++++++++++++++++++-------------------
hw/i386/kvm/pci-assign.c | 12 ++++--
hw/intc/ioapic.c | 28 +++++++++++--
hw/misc/ivshmem.c | 6 ++-
hw/vfio/pci.c | 6 ++-
hw/virtio/virtio-pci.c | 6 ++-
include/hw/i386/ioapic_internal.h | 1 +
include/hw/i386/x86-iommu.h | 1 +
include/sysemu/kvm.h | 7 ++--
kvm-all.c | 10 +++--
target-i386/kvm.c | 15 ++++---
11 files changed, 108 insertions(+), 66 deletions(-)
--
2.1.4
next reply other threads:[~2016-08-09 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 14:32 David Kiarie [this message]
2016-08-09 14:32 ` [Qemu-devel] [RFC 1/2] hw/msi: Allow platform devices to use explicit SID David Kiarie
2016-08-10 5:41 ` Peter Xu
2016-08-10 6:35 ` David Kiarie
2016-08-10 7:23 ` Peter Xu
2016-08-09 14:32 ` [Qemu-devel] [RFC 2/2] hw/i386: enforce SID verification David Kiarie
2016-08-09 18:41 ` Valentine Sinitsyn
2016-08-09 18:46 ` David Kiarie
2016-08-10 5:49 ` Peter Xu
2016-08-10 6:30 ` David Kiarie
2016-08-10 7:09 ` Peter Xu
2016-08-09 14:39 ` [Qemu-devel] [RFC 0/2] Explicit SID for IOAPIC no-reply
2016-08-09 14:39 ` 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=1470753137-18354-1-git-send-email-davidkiarie4@gmail.com \
--to=davidkiarie4@gmail.com \
--cc=ehabkost@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=valentine.sinitsyn@gmail.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).