From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Kiarie <davidkiarie4@gmail.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
Jan Kiszka <jan.kiszka@web.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [V6 4/4] hw/pci-host: Emulate AMD IOMMU
Date: Thu, 3 Mar 2016 11:49:35 +0200 [thread overview]
Message-ID: <20160303114709-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <CABdVeAAyjO_3pezxJbd7+MZhw5=rN=b14rKh=Jjt0S5=xwwzxg@mail.gmail.com>
On Thu, Mar 03, 2016 at 01:04:31AM +0300, David Kiarie wrote:
> On Thu, Mar 3, 2016 at 12:17 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > On Thu, Mar 03, 2016 at 12:09:28AM +0300, David Kiarie wrote:
> >>
> >>
> >> On 22/02/16 14:22, Marcel Apfelbaum wrote:
> >> >On 02/21/2016 08:11 PM, David Kiarie wrote:
> >> >>Add AMD IOMMU emulation support to q35 chipset
> >> >>
> >> >>Signed-off-by: David Kiarie <davidkiarie4@gmail.com>
> >> >>---
> >> >> hw/pci-host/piix.c | 1 +
> >> >> hw/pci-host/q35.c | 14 ++++++++++++--
> >> >> include/hw/i386/intel_iommu.h | 1 +
> >> >> 3 files changed, 14 insertions(+), 2 deletions(-)
> >> >>
> >> >>diff --git a/hw/pci-host/piix.c b/hw/pci-host/piix.c
> >> >>index 41aa66f..ab2e24a 100644
> >> >>--- a/hw/pci-host/piix.c
> >> >>+++ b/hw/pci-host/piix.c
> >> >>@@ -36,6 +36,7 @@
> >> >> #include "hw/i386/ioapic.h"
> >> >> #include "qapi/visitor.h"
> >> >> #include "qemu/error-report.h"
> >> >>+#include "hw/i386/amd_iommu.h"
> >> >
> >> >Hi,
> >> >
> >> >I think you don't need this include anymore.
> >> >
> >> >>
> >> >> /*
> >> >> * I440FX chipset data sheet.
> >> >>diff --git a/hw/pci-host/q35.c b/hw/pci-host/q35.c
> >> >>index 115fb8c..355fb32 100644
> >> >>--- a/hw/pci-host/q35.c
> >> >>+++ b/hw/pci-host/q35.c
> >> >>@@ -31,6 +31,7 @@
> >> >> #include "hw/hw.h"
> >> >> #include "hw/pci-host/q35.h"
> >> >> #include "qapi/visitor.h"
> >> >>+#include "hw/i386/amd_iommu.h"
> >> >>
> >> >>/****************************************************************************
> >> >> * Q35 host
> >> >>@@ -505,9 +506,18 @@ static void mch_realize(PCIDevice *d, Error **errp)
> >> >> mch->pci_address_space, &mch->pam_regions[i+1],
> >> >> PAM_EXPAN_BASE + i * PAM_EXPAN_SIZE, PAM_EXPAN_SIZE);
> >> >> }
> >> >>- /* Intel IOMMU (VT-d) */
> >> >>- if (object_property_get_bool(qdev_get_machine(), "iommu", NULL)) {
> >> >>+
> >> >>+ if (g_strcmp0(MACHINE(qdev_get_machine())->iommu, INTEL_IOMMU_STR)
> >> >>== 0) {
> >> >>+ /* Intel IOMMU (VT-d) */
> >> >> mch_init_dmar(mch);
> >> >>+ } else if (g_strcmp0(MACHINE(qdev_get_machine())->iommu,
> >> >>AMD_IOMMU_STR)
> >> >>+ == 0) {
> >> >>+ AMDIOMMUState *iommu_state;
> >> >>+ PCIDevice *iommu;
> >> >>+ PCIBus *bus = PCI_BUS(qdev_get_parent_bus(DEVICE(mch)));
> >> >>+ iommu = pci_create_simple(bus, 0x20, TYPE_AMD_IOMMU_DEVICE);
> >
> > Pls don't hardcode paths like this. Set addr property instead.
> >
> >> >>+ iommu_state = AMD_IOMMU_DEVICE(iommu);
> >> >>+ pci_setup_iommu(bus, bridge_host_amd_iommu, iommu_state);
> >> >
> >> >pci_setup_iommu third parameter is void*, so you don't need to cast to
> >> >AMDIOMMUState
> >> >before passing it.
> >>
> >> This include is necessary for the definition of "AMD_IOMMU_STR" either way
> >> so am leaving this as is.
> >
> > This option parsing is just too ugly.
> >
> > Looks like it was a mistake to support the iommu
> > machine property, but I see no reason to add to the
> > existing mess.
> >
> > Can't users create iommu with -device amd-iommu ?
>
> You mean getting rid of the above code and starting device with
> '-device amd-iommu' ? This way am not able to setup IOMMU regions for
> devices correctly. IIRC 'pci_setup_iommu' when called from IOMMU code
> sets up IOMMU region for IOMMU only. Calling this from the bus sets up
> IOMMU regions for all devices though.
>
> I need to setup IOMMU regions for all devices from the bus, to be able
> to do that I need to have created the IOMMU device first.
I agree it's unfortunate, but I don't think internal limitations
should affect the user interface like this.
I wish we had a way to specify initialization order for devices in some
way, such that system devices are created before others.
For now, can you call pci_setup_iommu in the machine done callback?
> >
> > It's necessary if we are to support multiple IOMMUs, anyway.
> >
> >> >
> >> >Thanks,
> >> >Marcel
> >> >
> >> >> }
> >> >> }
> >> >>
> >> >>diff --git a/include/hw/i386/intel_iommu.h
> >> >>b/include/hw/i386/intel_iommu.h
> >> >>index b024ffa..539530c 100644
> >> >>--- a/include/hw/i386/intel_iommu.h
> >> >>+++ b/include/hw/i386/intel_iommu.h
> >> >>@@ -27,6 +27,7 @@
> >> >> #define TYPE_INTEL_IOMMU_DEVICE "intel-iommu"
> >> >> #define INTEL_IOMMU_DEVICE(obj) \
> >> >> OBJECT_CHECK(IntelIOMMUState, (obj), TYPE_INTEL_IOMMU_DEVICE)
> >> >>+#define INTEL_IOMMU_STR "intel"
> >> >>
> >> >> /* DMAR Hardware Unit Definition address (IOMMU unit) */
> >> >> #define Q35_HOST_BRIDGE_IOMMU_ADDR 0xfed90000ULL
> >> >>
> >> >
next prev parent reply other threads:[~2016-03-03 9:49 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 18:10 [Qemu-devel] [V6 0/4] AMD IOMMU David Kiarie
2016-02-21 18:10 ` [Qemu-devel] [V6 1/4] hw/i386: Introduce " David Kiarie
2016-02-25 15:43 ` Marcel Apfelbaum
2016-02-26 6:23 ` David Kiarie
2016-03-02 4:00 ` David Kiarie
2016-03-02 4:08 ` David Kiarie
2016-03-03 9:40 ` Marcel Apfelbaum
2016-03-03 9:34 ` Marcel Apfelbaum
2016-03-02 19:11 ` David Kiarie
2016-03-03 12:16 ` Marcel Apfelbaum
2016-02-21 18:10 ` [Qemu-devel] [V6 2/4] hw/core: Add AMD IOMMU to machine properties David Kiarie
2016-02-21 20:09 ` Jan Kiszka
2016-03-02 20:51 ` David Kiarie
2016-03-03 9:28 ` Marcel Apfelbaum
2016-03-11 13:20 ` Michael S. Tsirkin
2016-02-21 18:10 ` [Qemu-devel] [V6 3/4] hw/i386: ACPI table for AMD IOMMU David Kiarie
2016-02-21 18:20 ` Jan Kiszka
2016-02-21 19:00 ` David Kiarie
2016-02-21 18:11 ` [Qemu-devel] [V6 4/4] hw/pci-host: Emulate " David Kiarie
2016-02-22 11:22 ` Marcel Apfelbaum
[not found] ` <56D75688.1020500@gmail.com>
2016-03-02 21:17 ` Michael S. Tsirkin
2016-03-02 22:04 ` David Kiarie
2016-03-03 9:49 ` Michael S. Tsirkin [this message]
2016-03-03 11:47 ` David Kiarie
2016-03-03 12:02 ` Marcel Apfelbaum
2016-03-03 12:06 ` Marcel Apfelbaum
2016-03-03 12:18 ` David Kiarie
2016-03-03 12:58 ` Michael S. Tsirkin
2016-03-08 17:15 ` David Kiarie
2016-03-11 13:22 ` Michael S. Tsirkin
2016-03-13 0:14 ` David Kiarie
2016-03-13 13:59 ` Michael S. Tsirkin
2016-02-21 20:20 ` [Qemu-devel] [V6 0/4] " Jan Kiszka
2016-02-22 5:57 ` David Kiarie
2016-02-22 7:29 ` Jan Kiszka
2016-02-22 11:05 ` David Kiarie
2016-02-22 11:12 ` Jan Kiszka
2016-03-01 13:07 ` Michael S. Tsirkin
2016-03-01 13:48 ` Jan Kiszka
2016-03-01 13:55 ` Michael S. Tsirkin
2016-03-01 14:12 ` Jan Kiszka
2016-03-01 14:18 ` Jan Kiszka
2016-03-01 14:30 ` Michael S. Tsirkin
2016-03-01 14:35 ` Jan Kiszka
2016-03-01 14:19 ` Michael S. Tsirkin
2016-03-01 14:00 ` Jan Kiszka
2016-03-01 20:11 ` Michael S. Tsirkin
2016-03-01 20:17 ` Jan Kiszka
2016-03-01 20:39 ` Michael S. Tsirkin
2016-03-01 21:23 ` Jan Kiszka
2016-03-01 22:35 ` Michael S. Tsirkin
2016-03-02 21:17 ` David Kiarie
2016-03-02 21:32 ` 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=20160303114709-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=davidkiarie4@gmail.com \
--cc=jan.kiszka@web.de \
--cc=marcel@redhat.com \
--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).