From: Will Deacon <will@kernel.org>
To: Tomasz Jeznach <tjeznach@rivosinc.com>
Cc: Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <apatel@ventanamicro.com>,
Sunil V L <sunilvl@ventanamicro.com>,
Nick Kossifidis <mick@ics.forth.gr>,
Sebastien Boeuf <seb@rivosinc.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, iommu@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux@rivosinc.com
Subject: Re: [PATCH v10 0/7] Linux RISC-V IOMMU Support
Date: Thu, 24 Oct 2024 14:09:15 +0100 [thread overview]
Message-ID: <20241024130914.GF30704@willie-the-truck> (raw)
In-Reply-To: <cover.1729059707.git.tjeznach@rivosinc.com>
On Tue, Oct 15, 2024 at 11:52:12PM -0700, Tomasz Jeznach wrote:
> This patch series introduces support for RISC-V IOMMU architected
> hardware into the Linux kernel.
>
> The RISC-V IOMMU specification, which this series is based on, is
> ratified and available at GitHub/riscv-non-isa [1].
>
> At a high level, the RISC-V IOMMU specification defines:
>
> 1) Data structures:
> - Device-context: Associates devices with address spaces and holds
> per-device parameters for address translations.
> - Process-contexts: Associates different virtual address spaces based
> on device-provided process identification numbers.
> - MSI page table configuration used to direct an MSI to a guest
> interrupt file in an IMSIC.
> 2) In-memory queue interface:
> - Command-queue for issuing commands to the IOMMU.
> - Fault/event queue for reporting faults and events.
> - Page-request queue for reporting "Page Request" messages received
> from PCIe devices.
> - Message-signaled and wire-signaled interrupt mechanisms.
> 3) Memory-mapped programming interface:
> - Mandatory and optional register layout and description.
> - Software guidelines for device initialization and capabilities discovery.
>
>
> This series introduces RISC-V IOMMU hardware initialization and complete
> single-stage translation with paging domain support.
>
> The patches are organized as follows:
>
> Patch 1: Introduces minimal required device tree bindings for the driver.
> Patch 2: Defines RISC-V IOMMU data structures, hardware programming interface
> registers layout, and minimal initialization code for enabling global
> pass-through for all connected masters.
> Patch 3: Implements the device driver for PCIe implementation of RISC-V IOMMU
> architected hardware.
> Patch 4: Introduces IOMMU interfaces to the kernel subsystem.
> Patch 5: Implements device directory management with discovery sequences for
> I/O mapped or in-memory device directory table location, hardware
> capabilities discovery, and device to domain attach implementation.
> Patch 6: Implements command and fault queue, and introduces directory cache
> invalidation sequences.
> Patch 7: Implements paging domain, using highest page-table mode advertised
> by the hardware. This series enables only 4K mappings; complete support
> for large page mappings will be introduced in follow-up patch series.
>
> Follow-up patch series providing MSI interrupt remapping, complete ATS/PRI/SVA
> and VFIO/IOMMUFD support are available at the GitHub [2], and has been tested
> with published QEMU RISC-V IOMMU device model [3].
>
> Changes from v9:
> - rebase on v6.12-rc3
> - #6 Memory ordering fix and updated commentary, based on Will’s suggestions.
> - #7 Remove riscv_iommu_device_domain_type() and use head-less kfree_rcu in
> riscv_iommu_release_device(), based on Jason's suggestions.
Thanks, looks ok to me now.
Will
next prev parent reply other threads:[~2024-10-24 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 6:52 [PATCH v10 0/7] Linux RISC-V IOMMU Support Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 1/7] dt-bindings: iommu: riscv: Add bindings for RISC-V IOMMU Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 2/7] iommu/riscv: Add RISC-V IOMMU platform device driver Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 3/7] iommu/riscv: Add RISC-V IOMMU PCIe " Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 4/7] iommu/riscv: Enable IOMMU registration and device probe Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 5/7] iommu/riscv: Device directory management Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 6/7] iommu/riscv: Command and fault queue support Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 7/7] iommu/riscv: Paging domain support Tomasz Jeznach
2024-10-16 23:58 ` [PATCH v10 0/7] Linux RISC-V IOMMU Support Palmer Dabbelt
2024-10-24 13:09 ` Will Deacon [this message]
2024-10-29 8:42 ` Joerg Roedel
2025-11-05 10:08 ` Vivian Wang
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=20241024130914.GF30704@willie-the-truck \
--to=will@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=seb@rivosinc.com \
--cc=sunilvl@ventanamicro.com \
--cc=tjeznach@rivosinc.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