From: Tomasz Jeznach <tjeznach@rivosinc.com>
To: Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Weiwei Li" <liweiwei@iscas.ac.cn>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org, linux@rivosinc.com,
"Tomasz Jeznach" <tjeznach@rivosinc.com>
Subject: [PATCH 0/5] QEMU RISC-V IOMMU Support
Date: Wed, 19 Jul 2023 19:32:53 -0700 [thread overview]
Message-ID: <cover.1689819031.git.tjeznach@rivosinc.com> (raw)
The RISC-V IOMMU specification is now ratified as-per the RISC-V international
process [1]. The latest frozen specifcation can be found at:
https://github.com/riscv-non-isa/riscv-iommu/releases/download/v1.0/riscv-iommu.pdf
This series introduces a RISC-V IOMMU device emulation implementation with two stage
address translation logic, device and process translation context mapping and queue
interfaces, along with riscv/virt machine bindings (patch 5) and memory attributes
extensions for PASID support (patch 3,4).
This series is based on incremental patches created during RISC-V International IOMMU
Task Group discussions and specification development process, with original series
available in the the maintainer's repository branch [2].
These patches can also be found in the riscv_iommu_v1 branch at:
https://github.com/tjeznach/qemu/tree/riscv_iommu_v1
To test this series, use Linux v6.5-rc2 with RISC-V IOMMU implementation available in
the riscv_iommu_v1 branch at:
https://github.com/tjeznach/linux/tree/riscv_iommu_v1
References:
[1] - https://wiki.riscv.org/display/HOME/Specification+Status
[2] - https://github.com/tjeznach/qemu/tree/tjeznach/riscv-iommu-20230719
Tomasz Jeznach (5):
hw/riscv: Introduction of RISC-V IOMMU device
MAINTAINERS: Add RISC-V IOMMU maintainers
exec/memtxattr: add process identifier to the transaction attributes
hw/riscv: IOMMU: use process identifier from transaction attributes.
hw/riscv: virt: support for RISC-V IOMMU platform device.
MAINTAINERS | 6 +
hw/riscv/Kconfig | 4 +
hw/riscv/meson.build | 1 +
hw/riscv/riscv-iommu-bits.h | 749 +++++++++++
hw/riscv/riscv-iommu-pci.c | 181 +++
hw/riscv/riscv-iommu-sys.c | 123 ++
hw/riscv/riscv-iommu.c | 2546 +++++++++++++++++++++++++++++++++++
hw/riscv/riscv-iommu.h | 152 +++
hw/riscv/trace-events | 14 +
hw/riscv/trace.h | 2 +
hw/riscv/virt.c | 100 +-
include/exec/memattrs.h | 6 +
include/hw/riscv/iommu.h | 40 +
include/hw/riscv/virt.h | 3 +
meson.build | 1 +
15 files changed, 3927 insertions(+), 1 deletion(-)
create mode 100644 hw/riscv/riscv-iommu-bits.h
create mode 100644 hw/riscv/riscv-iommu-pci.c
create mode 100644 hw/riscv/riscv-iommu-sys.c
create mode 100644 hw/riscv/riscv-iommu.c
create mode 100644 hw/riscv/riscv-iommu.h
create mode 100644 hw/riscv/trace-events
create mode 100644 hw/riscv/trace.h
create mode 100644 include/hw/riscv/iommu.h
--
2.34.1
next reply other threads:[~2023-07-20 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 2:32 Tomasz Jeznach [this message]
2023-07-20 2:32 ` [PATCH 1/5] hw/riscv: Introduction of RISC-V IOMMU device Tomasz Jeznach
2023-07-24 2:32 ` Alistair Francis
2023-08-07 16:16 ` Tomasz Jeznach
2023-07-20 2:32 ` [PATCH 2/5] MAINTAINERS: Add RISC-V IOMMU maintainers Tomasz Jeznach
2023-07-20 2:32 ` [PATCH 3/5] exec/memtxattr: add process identifier to the transaction attributes Tomasz Jeznach
2023-07-20 2:32 ` [PATCH 4/5] hw/riscv: IOMMU: use process identifier from " Tomasz Jeznach
2023-07-20 2:32 ` [PATCH 5/5] hw/riscv: virt: support for RISC-V IOMMU platform device Tomasz Jeznach
2023-07-24 2:35 ` Alistair Francis
2023-08-07 16:21 ` Tomasz Jeznach
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.1689819031.git.tjeznach@rivosinc.com \
--to=tjeznach@rivosinc.com \
--cc=alistair.francis@wdc.com \
--cc=berrange@redhat.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=linux@rivosinc.com \
--cc=liweiwei@iscas.ac.cn \
--cc=marcandre.lureau@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=thuth@redhat.com \
--cc=zhiwei_liu@linux.alibaba.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).