From: Wang Xingang <wangxingang5@huawei.com>
To: <qemu-devel@nongnu.org>, <qemu-arm@nongnu.org>, <eric.auger@redhat.com>
Cc: xieyingtai@huawei.com, peter.maydell@linaro.org,
cenjiahui@huawei.com, ehabkost@redhat.com, mst@redhat.com,
richard.henderson@linaro.org, shannon.zhaosl@gmail.com,
pbonzini@redhat.com, imammedo@redhat.com,
wangxingang5@huawei.com
Subject: [PATCH RFC v2 0/6] Introduce IOMMU Option For PCI Root Bus
Date: Wed, 24 Mar 2021 13:16:29 +0000 [thread overview]
Message-ID: <1616591795-2056-1-git-send-email-wangxingang5@huawei.com> (raw)
From: Xingang Wang <wangxingang5@huawei.com>
These patches add support for configure iommu on/off for pci root bus,
including primary bus and pxb root bus. At present, All root bus
will go through iommu when iommu is configured, which is not flexible.
So this add option to enable/disable iommu for primary bus and pxb
root bus. When iommu is enabled for the root bus, devices attached to it
will go through iommu. When iommu is disabled for the root bus, devices
will not go through iommu accordingly.
The option example for iommu configuration is like the following:
primary root bus option:
arm: -machine virt iommu=smmuv3,primary_bus_iommu=false(or true)
x86: -machine q35,primary_bus_iommu=false(or true)
pxb root bus:
-device pxb-pcie,bus_nr=0x10,id=pci.10,bus=pcie.0,addr=0x3.0x1,iommu=false
History:
v1 -> v2:
- Fix some issues
- Took into account Eric's comments, and remove the PCI_BUS_IOMMU flag,
replace it with a property in PCIHostState.
- Add support for x86 iommu option
Xingang Wang (6):
hw/pci/pci_host: Add iommu property for pci host
hw/pci: Add iommu option for pci root bus
hw/pci: Add pci_root_bus_max_bus
hw/arm/virt-acpi-build: Add explicit idmap info in IORT table
hw/i386/acpi-build: Add explicit scope in DMAR table
hw/i386/acpi-build: Add iommu filter in IVRS table
hw/arm/virt-acpi-build.c | 103 ++++++++++++++++++++++------
hw/arm/virt.c | 25 +++++++
hw/i386/acpi-build.c | 70 ++++++++++++++++++-
hw/i386/pc.c | 19 +++++
hw/pci-bridge/pci_expander_bridge.c | 3 +
hw/pci-host/q35.c | 1 +
hw/pci/pci.c | 52 +++++++++++++-
hw/pci/pci_host.c | 2 +
include/hw/arm/virt.h | 1 +
include/hw/i386/pc.h | 1 +
include/hw/pci/pci.h | 2 +
include/hw/pci/pci_host.h | 1 +
12 files changed, 254 insertions(+), 26 deletions(-)
--
2.19.1
next reply other threads:[~2021-03-24 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 13:16 Wang Xingang [this message]
2021-03-24 13:16 ` [PATCH RFC v2 1/6] hw/pci/pci_host: Add iommu property for pci host Wang Xingang
2021-03-24 13:16 ` [PATCH RFC v2 2/6] hw/pci: Add iommu option for pci root bus Wang Xingang
2021-03-24 13:16 ` [PATCH RFC v2 3/6] hw/pci: Add pci_root_bus_max_bus Wang Xingang
2021-03-24 13:16 ` [PATCH RFC v2 4/6] hw/arm/virt-acpi-build: Add explicit idmap info in IORT table Wang Xingang
2021-03-24 13:16 ` [PATCH RFC v2 5/6] hw/i386/acpi-build: Add explicit scope in DMAR table Wang Xingang
2021-03-24 13:16 ` [PATCH RFC v2 6/6] hw/i386/acpi-build: Add iommu filter in IVRS table Wang Xingang
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=1616591795-2056-1-git-send-email-wangxingang5@huawei.com \
--to=wangxingang5@huawei.com \
--cc=cenjiahui@huawei.com \
--cc=ehabkost@redhat.com \
--cc=eric.auger@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shannon.zhaosl@gmail.com \
--cc=xieyingtai@huawei.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).