From: Jason Chien <jason.chien@sifive.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Jason Chien <jason.chien@sifive.com>
Subject: [PATCH 0/3] Enhancing Device Identification in RISC-V IOMMU Using Memory Attributes
Date: Sun, 2 Mar 2025 17:12:06 +0800 [thread overview]
Message-ID: <20250302091209.20063-1-jason.chien@sifive.com> (raw)
This patch series enhances how device IDs are handled in RISC-V IOMMU by
leveraging memory attributes.
The BDF (Bus-Device-Function) is now included in memory attributes for
DMA operations, ensuring accurate device identification.
Since PCIe bus numbers can change after re-enumeration, relying on static
device IDs in RISCVIOMMUSpace may lead to incorrect Device Directory Table
walk. The IOMMU now dynamically retrieves latest device IDs from memory
attributes.
The bus property, previously used to set non-root endpoint bus numbers,
is removed. As PCIe bus numbers are assigned at runtime and vary across
endpoints, exposing a single property to pre-set them is unnecessary and
incorrect. With device IDs now retrieved dynamically, this property is no
longer required.
Jason Chien (3):
include/hw/pci: Attach BDF to Memory Attributes
hw/riscv/riscv-iommu: Obtain Device IDs from Memory Attributes
hw/riscv/riscv_iommu: Remove the "bus" property
hw/riscv/riscv-iommu.c | 15 +++++++--------
hw/riscv/riscv-iommu.h | 1 -
include/hw/pci/pci_device.h | 10 ++++++++--
3 files changed, 15 insertions(+), 11 deletions(-)
--
2.43.2
next reply other threads:[~2025-03-02 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 9:12 Jason Chien [this message]
2025-03-02 9:12 ` [PATCH 1/3] include/hw/pci: Attach BDF to Memory Attributes Jason Chien
2025-03-07 12:39 ` Daniel Henrique Barboza
2025-03-12 16:59 ` Jason Chien
2025-03-19 16:40 ` Jason Chien
2025-04-14 15:10 ` Jason Chien
2025-04-14 15:28 ` Michael S. Tsirkin
2025-04-24 7:57 ` Jason Chien
2025-03-02 9:12 ` [PATCH 2/3] hw/riscv/riscv-iommu: Obtain Device IDs from " Jason Chien
2025-03-07 12:35 ` Daniel Henrique Barboza
2025-03-02 9:12 ` [PATCH 3/3] hw/riscv/riscv_iommu: Remove the "bus" property Jason Chien
2025-03-07 12:36 ` Daniel Henrique Barboza
2025-04-04 1:43 ` Alistair Francis
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=20250302091209.20063-1-jason.chien@sifive.com \
--to=jason.chien@sifive.com \
--cc=alistair.francis@wdc.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--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).