Message ID | 20230508142842.854564-1-apatel@ventanamicro.com (mailing list archive) |
---|---|
Headers | show |
Series | Linux RISC-V AIA Support | expand |
Hey Anup, On Mon, May 08, 2023 at 07:58:31PM +0530, Anup Patel wrote: > The RISC-V AIA specification is now frozen as-per the RISC-V international > process. The latest frozen specifcation can be found at: > https://github.com/riscv/riscv-aia/releases/download/1.0-RC1/riscv-interrupts-1.0-RC1.pdf > > At a high-level, the AIA specification adds three things: > 1) AIA CSRs > - Improved local interrupt support > 2) Incoming Message Signaled Interrupt Controller (IMSIC) > - Per-HART MSI controller > - Support MSI virtualization > - Support IPI along with virtualization > 3) Advanced Platform-Level Interrupt Controller (APLIC) > - Wired interrupt controller > - In MSI-mode, converts wired interrupt into MSIs (i.e. MSI generator) > - In Direct-mode, injects external interrupts directly into HARTs > > For an overview of the AIA specification, refer the recent AIA virtualization > talk at KVM Forum 2022: > https://static.sched.com/hosted_files/kvmforum2022/a1/AIA_Virtualization_in_KVM_RISCV_final.pdf > https://www.youtube.com/watch?v=r071dL8Z0yo > > The PATCH3 of this series conflicts with the "irqchip/riscv-intc: Add ACPI > support" patch of the "Add basic ACPI support for RISC-V" series. > (Refer, https://lore.kernel.org/linux-riscv/20230508115237.216337-1-sunilvl@ventanamicro.com/) This series does not apply for me (or the patchwork automation) on top of v6.4-rc1, which was released prior to you sending this & contains the AIA definitions this series relies on. You note here that there is a *conflict* with Sunil's series, but what you actually did, as far as I can tell, is base your series on top of theirs? If you're going to do that, at least point it out so that reviewers don't have to figure out what your intention was :( Better yet, for the sake of our automation in particular, don't do it at all. Thanks, Conor.