RISC-V AIA irqchip and Svnapot support
Subsystems (4)
cover RISC-V AIA irqchip and Svnapot support
The latest KVM in Linux-6.5 has support for:
1) Svnapot ISA extension support
2) AIA in-kernel irqchip support
This series adds corresponding changes in KVMTOOL to use the above mentioned features for Guest/VM.
These patches can also be found in the riscv_aia_v1 branch at:
https://github.com/avpatel/kvmtool.git
Anup Patel (6):
Sync-up header with Linux-6.5-rc3 for KVM RISC-V
riscv: Add Svnapot extension support
riscv: Make irqchip support pluggable
riscv: Add IRQFD support for in-kernel AIA irqchip
riscv: Use AIA in-kernel irqchip whenever KVM RISC-V supports
riscv: Fix guest/init linkage for multilib toolchain
Makefile | 3 + include/linux/kvm.h | 6 +- riscv/aia.c | 227 ++++++++++++++++++++++++++++ riscv/fdt.c | 15 +- riscv/include/asm/kvm.h | 81 ++++++++++ riscv/include/kvm/fdt-arch.h | 8 +- riscv/include/kvm/kvm-arch.h | 38 ++++- riscv/include/kvm/kvm-config-arch.h | 3 + riscv/irq.c | 138 ++++++++++++++++- riscv/kvm.c | 2 + riscv/pci.c | 32 ++-- riscv/plic.c | 61 ++++---- 12 files changed, 563 insertions(+), 51 deletions(-) create mode 100644 riscv/aia.c
Signature · 1 line
2.34.1
PATCH 1/6 Sync-up header with Linux-6.5-rc3 for KVM RISC-V
We sync-up Linux headers to get latest KVM RISC-V headers having V, Svnapot, and AIA support.
--- include/linux/kvm.h | 6 ++- riscv/include/asm/kvm.h | 81 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 86 insertions(+), 1 deletion(-)
include/linux/kvm.h +5 -1
@@ -1190,6 +1190,8 @@ struct kvm_ppc_resize_hpt {#define KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP 225#define KVM_CAP_PMU_EVENT_MASKED_EVENTS 226#define KVM_CAP_COUNTER_OFFSET 227 +#define KVM_CAP_ARM_EAGER_SPLIT_CHUNK_SIZE 228 +#define KVM_CAP_ARM_SUPPORTED_BLOCK_SIZES 229#ifdef KVM_CAP_IRQ_ROUTING
@@ -1442,6 +1444,8 @@ enum kvm_device_type {#define KVM_DEV_TYPE_XIVE KVM_DEV_TYPE_XIVE KVM_DEV_TYPE_ARM_PV_TIME,#define KVM_DEV_TYPE_ARM_PV_TIME KVM_DEV_TYPE_ARM_PV_TIME + KVM_DEV_TYPE_RISCV_AIA, +#define KVM_DEV_TYPE_RISCV_AIA KVM_DEV_TYPE_RISCV_AIA KVM_DEV_TYPE_MAX, };
@@ -1613,7 +1617,7 @@ struct kvm_s390_ucas_mapping {#define KVM_GET_DEBUGREGS _IOR(KVMIO, 0xa1, struct kvm_debugregs)#define KVM_SET_DEBUGREGS _IOW(KVMIO, 0xa2, struct kvm_debugregs)/* -* vcpu version available with KVM_ENABLE_CAP +* vcpu version available with KVM_CAP_ENABLE_CAP * vm version available with KVM_CAP_ENABLE_CAP_VM */ #define KVM_ENABLE_CAP _IOW(KVMIO, 0xa3, struct kvm_enable_cap)
riscv/include/asm/kvm.h +81 -0
99 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 2/6 riscv: Add Svnapot extension support
In reply to Anup PatelWhen the Svnapot extension is available expose it to the guest via device tree so that guest can use it.
--- riscv/fdt.c | 1 + riscv/include/kvm/kvm-config-arch.h | 3 +++ 2 files changed, 4 insertions(+)
riscv/fdt.c +1 -0
@@ -19,6 +19,7 @@ struct isa_ext_info isa_info_arr[] = { {"ssaia", KVM_RISCV_ISA_EXT_SSAIA}, {"sstc", KVM_RISCV_ISA_EXT_SSTC}, {"svinval", KVM_RISCV_ISA_EXT_SVINVAL}, + {"svnapot", KVM_RISCV_ISA_EXT_SVNAPOT}, {"svpbmt", KVM_RISCV_ISA_EXT_SVPBMT}, {"zbb", KVM_RISCV_ISA_EXT_ZBB}, {"zicbom", KVM_RISCV_ISA_EXT_ZICBOM},
riscv/include/kvm/kvm-config-arch.h +3 -0
@@ -34,6 +34,9 @@ struct kvm_config_arch {OPT_BOOLEAN ('\0' ,"disable-svinval" , \ &(cfg)->ext_disabled[KVM_RISCV_ISA_EXT_SVINVAL ], \"Disable Svinval Extension" ), \ +OPT_BOOLEAN ('\0' ,"disable-svnapot" , \ + &(cfg)->ext_disabled[KVM_RISCV_ISA_EXT_SVNAPOT ], \ +"Disable Svnapot Extension" ), \OPT_BOOLEAN ('\0' ,"disable-svpbmt" , \ &(cfg)->ext_disabled[KVM_RISCV_ISA_EXT_SVPBMT ], \ "Disable Svpbmt Extension"), \
Signature · 1 line
2.34.1
PATCH 3/6 riscv: Make irqchip support pluggable
In reply to Anup PatelWe will be having different types of irqchip:
1) PLIC emulated by user-space
2) AIA APLIC and IMSIC provided by in-kernel KVM module
To support above, we de-couple PLIC specific code from generic RISC-V code (such as FDT generation) so that we can easily add other types of irqchip.
--- riscv/fdt.c | 14 ++++++-- riscv/include/kvm/kvm-arch.h | 25 ++++++++++++--- riscv/irq.c | 62 ++++++++++++++++++++++++++++++++++-- riscv/kvm.c | 2 ++ riscv/pci.c | 32 +++++++++++++------ riscv/plic.c | 61 +++++++++++++++++------------------ 6 files changed, 147 insertions(+), 49 deletions(-)
riscv/fdt.c +11 -3
@@ -209,19 +209,26 @@ static int setup_fdt(struct kvm *kvm)/* CPUs */ generate_cpu_nodes (fdt, kvm); +/* IRQCHIP */ +if (!riscv_irqchip_generate_fdt_node) +die ("No way to generate IRQCHIP FDT node\n" ); +riscv_irqchip_generate_fdt_node (fdt, kvm); +/* Simple Bus */ _FDT (fdt_begin_node (fdt,"smb" ));_FDT (fdt_property_string (fdt,"compatible" ,"simple-bus" ));_FDT (fdt_property_cell (fdt,"#address-cells" ,0x2 ));_FDT (fdt_property_cell (fdt,"#size-cells" ,0x2 )); -_FDT (fdt_property_cell (fdt,"interrupt-parent" ,PHANDLE_PLIC )); +_FDT (fdt_property_cell (fdt,"interrupt-parent" , + riscv_irqchip_phandle));_FDT (fdt_property (fdt,"ranges" ,NULL ,0 ));/* Virtio MMIO devices */ dev_hdr =device__first_dev (DEVICE_BUS_MMIO );while (dev_hdr) { generate_mmio_fdt_nodes = dev_hdr->data; -generate_mmio_fdt_nodes (fdt, dev_hdr, plic__generate_irq_prop); +generate_mmio_fdt_nodes (fdt, dev_hdr, + riscv__generate_irq_prop); dev_hdr =device__next_dev (dev_hdr); }
@@ -229,7 +236,8 @@ static int setup_fdt(struct kvm *kvm) dev_hdr =device__first_dev (DEVICE_BUS_IOPORT );while (dev_hdr) { generate_mmio_fdt_nodes = dev_hdr->data; -generate_mmio_fdt_nodes (fdt, dev_hdr, plic__generate_irq_prop); +generate_mmio_fdt_nodes (fdt, dev_hdr, + riscv__generate_irq_prop); dev_hdr =device__next_dev (dev_hdr); }
riscv/include/kvm/kvm-arch.h +21 -4
@@ -10,8 +10,8 @@#define RISCV_IOPORT 0x00000000ULL#define RISCV_IOPORT_SIZE SZ_64K -#define RISCV_PLIC 0x0c000000ULL -#define RISCV_PLIC_SIZE SZ_64M +#define RISCV_IRQCHIP 0x08000000ULL +#define RISCV_IRQCHIP_SIZE SZ_128M#define RISCV_MMIO 0x10000000ULL#define RISCV_MMIO_SIZE SZ_512M#define RISCV_PCI 0x30000000ULL
@@ -84,10 +84,27 @@ static inline bool riscv_addr_in_ioport_region(u64 phys_addr)enum irq_type ; -void plic__generate_irq_prop (void *fdt,u8 irq,enum irq_type irq_type); +enum irqchip_type { +IRQCHIP_UNKNOWN =0 , +IRQCHIP_PLIC , +IRQCHIP_AIA +}; + +extern enum irqchip_type riscv_irqchip; +extern bool riscv_irqchip_inkernel; +extern void (*riscv_irqchip_trigger)(struct kvm *kvm,int irq, +int level,bool edge); +extern void (*riscv_irqchip_generate_fdt_node)(void *fdt,struct kvm *kvm); +extern u32 riscv_irqchip_phandle; +extern u32 riscv_irqchip_msi_phandle; +extern bool riscv_irqchip_line_sensing; -void plic__irq_trig (struct kvm *kvm,int irq,int level,bool edge); +void plic__create (struct kvm *kvm);void pci__generate_fdt_nodes (void *fdt); +void riscv__generate_irq_prop (void *fdt,u8 irq,enum irq_type irq_type); + +void riscv__irqchip_create (struct kvm *kvm); +#endif /* KVM__KVM_ARCH_H */
riscv/irq.c +60 -2
73 lines not on this page · raw message
riscv/kvm.c +2 -0
@@ -96,6 +96,8 @@ void kvm__arch_init(struct kvm *kvm)madvise (kvm->arch.ram_alloc_start, kvm->arch.ram_alloc_size,MADV_HUGEPAGE ); + +riscv__irqchip_create (kvm); }#define FDT_ALIGN SZ_4M
riscv/pci.c +23 -9
@@ -7,20 +7,21 @@/* * An entry in the interrupt-map table looks like: -* <pci unit address> <pci interrupt pin> <plic phandle> <plic interrupt> +* <pci unit address> <pci interrupt pin> <irqchip phandle> <irqchip line> */ struct of_interrupt_map_entry {struct of_pci_irq_mask pci_irq_mask; -u32 plic_phandle; -u32 plic_irq; +u32 irqchip_phandle; +u32 irqchip_line; +u32 irqchip_sense; } __attribute__((packed));void pci__generate_fdt_nodes (void *fdt) {struct device_header *dev_hdr;struct of_interrupt_map_entry irq_map[OF_PCI_IRQ_MAP_MAX ]; -unsigned nentries =0 ; +unsigned nentries =0 , nsize;/* Bus range */ u32 bus_range[] = {cpu_to_fdt32 (0 ),cpu_to_fdt32 (1 ), };/* Configuration Space */
@@ -48,6 +49,11 @@ void pci__generate_fdt_nodes(void *fdt) }, }; +/* Find size of each interrupt map entery */ + nsize =sizeof (struct of_interrupt_map_entry ); +if (!riscv_irqchip_line_sensing) + nsize -=sizeof (u32); +/* Boilerplate PCI properties */ _FDT (fdt_begin_node (fdt,"pci" ));_FDT (fdt_property_string (fdt,"device_type" ,"pci" ));
@@ -64,12 +70,13 @@ void pci__generate_fdt_nodes(void *fdt)/* Generate the interrupt map ... */ dev_hdr =device__first_dev (DEVICE_BUS_PCI );while (dev_hdr && nentries <ARRAY_SIZE (irq_map)) { -struct of_interrupt_map_entry *entry = &irq_map[nentries]; +struct of_interrupt_map_entry *entry;struct pci_device_header *pci_hdr = dev_hdr->data;u8 dev_num = dev_hdr->dev_num;u8 pin = pci_hdr->irq_pin;u8 irq = pci_hdr->irq_line; + entry = ((void *)irq_map) + (nsize * nentries); *entry = (struct of_interrupt_map_entry ) { .pci_irq_mask = { .pci_addr = {
@@ -79,16 +86,18 @@ void pci__generate_fdt_nodes(void *fdt) }, .pci_pin = cpu_to_fdt32(pin), }, - .plic_phandle = cpu_to_fdt32(PHANDLE_PLIC), - .plic_irq = cpu_to_fdt32(irq), + .irqchip_phandle = cpu_to_fdt32(riscv_irqchip_phandle), + .irqchip_line = cpu_to_fdt32(irq), }; +if (riscv_irqchip_line_sensing) + entry->irqchip_sense =cpu_to_fdt32 (IRQ_TYPE_LEVEL_HIGH ); + nentries++; dev_hdr =device__next_dev (dev_hdr); } -_FDT (fdt_property (fdt,"interrupt-map" , irq_map, -sizeof (struct of_interrupt_map_entry ) * nentries)); +_FDT (fdt_property (fdt,"interrupt-map" , irq_map, nsize * nentries));/* ... and the corresponding mask. */ if (nentries) {
@@ -105,5 +114,10 @@ void pci__generate_fdt_nodes(void *fdt) sizeof(irq_mask))); } +/* Set MSI parent if available */ +if (riscv_irqchip_msi_phandle !=PHANDLE_RESERVED ) +_FDT (fdt_property_cell (fdt,"msi-parent" , + riscv_irqchip_msi_phandle)); +_FDT (fdt_end_node (fdt)); }
riscv/plic.c +30 -31
122 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 4/6 riscv: Add IRQFD support for in-kernel AIA irqchip
In reply to Anup PatelTo use irqfd with in-kernel AIA irqchip, we add custom irq__add_irqfd and irq__del_irqfd functions. This allows us to defer actual KVM_IRQFD ioctl() until AIA irqchip is initialized by KVMTOOL.
--- riscv/include/kvm/kvm-arch.h | 11 ++++++ riscv/irq.c | 73 ++++++++++++++++++++++++++++++++++++ 2 files changed, 84 insertions(+)
riscv/include/kvm/kvm-arch.h +11 -0
@@ -98,11 +98,22 @@ extern void (*riscv_irqchip_generate_fdt_node)(void *fdt, struct kvm *kvm);extern u32 riscv_irqchip_phandle;extern u32 riscv_irqchip_msi_phandle;extern bool riscv_irqchip_line_sensing; +extern bool riscv_irqchip_irqfd_ready;void plic__create (struct kvm *kvm);void pci__generate_fdt_nodes (void *fdt); +int riscv__add_irqfd (struct kvm *kvm,unsigned int gsi,int trigger_fd, +int resample_fd); + +void riscv__del_irqfd (struct kvm *kvm,unsigned int gsi,int trigger_fd); + +#define irq__add_irqfd riscv__add_irqfd +#define irq__del_irqfd riscv__del_irqfd + +int riscv__setup_irqfd_lines (struct kvm *kvm); +void riscv__generate_irq_prop (void *fdt,u8 irq,enum irq_type irq_type);void riscv__irqchip_create (struct kvm *kvm);
riscv/irq.c +73 -0
85 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 5/6 riscv: Use AIA in-kernel irqchip whenever KVM RISC-V supports
In reply to Anup PatelThe KVM RISC-V kernel module supports AIA in-kernel irqchip when underlying host has AIA support. We detect and use AIA in-kernel irqchip whenever possible otherwise we fallback to PLIC emulated in user-space.
--- Makefile | 1 + riscv/aia.c | 227 +++++++++++++++++++++++++++++++++++ riscv/include/kvm/fdt-arch.h | 8 +- riscv/include/kvm/kvm-arch.h | 2 + riscv/irq.c | 3 + 5 files changed, 240 insertions(+), 1 deletion(-) create mode 100644 riscv/aia.c
Makefile +1 -0
@@ -220,6 +220,7 @@ ifeq ($(ARCH),riscv) OBJS += riscv/kvm-cpu.o OBJS += riscv/pci.o OBJS += riscv/plic.o + OBJS += riscv/aia.o ifeq ($(RISCV_XLEN),32) CFLAGS += -mabi=ilp32d -march=rv32gc endif
riscv/aia.c new file +227 -0
227 lines not on this page · raw message
riscv/include/kvm/fdt-arch.h +7 -1
@@ -1,7 +1,13 @@#ifndef KVM__KVM_FDT_H #define KVM__KVM_FDT_H -enum phandles {PHANDLE_RESERVED =0 ,PHANDLE_PLIC ,PHANDLES_MAX }; +enum phandles { +PHANDLE_RESERVED =0 , +PHANDLE_PLIC , +PHANDLE_AIA_APLIC , +PHANDLE_AIA_IMSIC , +PHANDLES_MAX +};#define PHANDLE_CPU_INTC_BASE PHANDLES_MAX
riscv/include/kvm/kvm-arch.h +2 -0
@@ -100,6 +100,8 @@ extern u32 riscv_irqchip_msi_phandle;extern bool riscv_irqchip_line_sensing;extern bool riscv_irqchip_irqfd_ready; +void aia__create (struct kvm *kvm); +void plic__create (struct kvm *kvm);void pci__generate_fdt_nodes (void *fdt);
riscv/irq.c +3 -0
@@ -135,6 +135,9 @@ void riscv__generate_irq_prop(void *fdt, u8 irq, enum irq_type irq_type)void riscv__irqchip_create (struct kvm *kvm) { +/* Try AIA in-kernel irqchip. */ +aia__create (kvm); +/* Try PLIC irqchip */ plic__create (kvm);
Signature · 1 line
2.34.1
PATCH 6/6 riscv: Fix guest/init linkage for multilib toolchain
In reply to Anup PatelFor RISC-V multilib toolchains, we must specify -mabi and -march options when linking guest/init.
--- Makefile | 2 ++ 1 file changed, 2 insertions(+)
Makefile +2 -0
@@ -223,9 +223,11 @@ ifeq ($(ARCH),riscv) OBJS += riscv/aia.o ifeq ($(RISCV_XLEN),32) CFLAGS += -mabi=ilp32d -march=rv32gc + GUEST_INIT_FLAGS += -mabi=ilp32d -march=rv32gc endif ifeq ($(RISCV_XLEN),64) CFLAGS += -mabi=lp64d -march=rv64gc + GUEST_INIT_FLAGS += -mabi=lp64d -march=rv64gc endif ARCH_WANT_LIBFDT := y
Signature · 1 line
2.34.1
Hi Will,
Quoted 11 lines · On Tue, Jul 25, 2023 at 8:54?PM Anup Patel <[email protected]> wrote:
The latest KVM in Linux-6.5 has support for:
1) Svnapot ISA extension support
2) AIA in-kernel irqchip supportThis series adds corresponding changes in KVMTOOL to use the above mentioned features for Guest/VM.
These patches can also be found in the
riscv_aia_v1branch at:
https://github.com/avpatel/kvmtool.git
Quoted 7 lines
Anup Patel (6):
Sync-up header with Linux-6.5-rc3 for KVM RISC-V
riscv: Add Svnapot extension support
riscv: Make irqchip support pluggable
riscv: Add IRQFD support for in-kernel AIA irqchip
riscv: Use AIA in-kernel irqchip whenever KVM RISC-V supports
riscv: Fix guest/init linkage for multilib toolchain
Friendly ping ?
Regards,
Anup
Quoted 19 lines
Makefile | 3 + include/linux/kvm.h | 6 +- riscv/aia.c | 227 ++++++++++++++++++++++++++++ riscv/fdt.c | 15 +- riscv/include/asm/kvm.h | 81 ++++++++++ riscv/include/kvm/fdt-arch.h | 8 +- riscv/include/kvm/kvm-arch.h | 38 ++++- riscv/include/kvm/kvm-config-arch.h | 3 + riscv/irq.c | 138 ++++++++++++++++- riscv/kvm.c | 2 + riscv/pci.c | 32 ++-- riscv/plic.c | 61 ++++---- 12 files changed, 563 insertions(+), 51 deletions(-) create mode 100644 riscv/aia.c--
2.34.1
Quoted 20 lines · Anup Patel
Quoted 11 lines · On Tue, Jul 25, 2023 at 8:54?PM Anup Patel <[email protected]> wrote:
The latest KVM in Linux-6.5 has support for:
1) Svnapot ISA extension support
2) AIA in-kernel irqchip supportThis series adds corresponding changes in KVMTOOL to use the above mentioned features for Guest/VM.
These patches can also be found in the
riscv_aia_v1branch at:
https://github.com/avpatel/kvmtool.gitQuoted 7 lines
Anup Patel (6):
Sync-up header with Linux-6.5-rc3 for KVM RISC-V
riscv: Add Svnapot extension support
riscv: Make irqchip support pluggable
riscv: Add IRQFD support for in-kernel AIA irqchip
riscv: Use AIA in-kernel irqchip whenever KVM RISC-V supports
riscv: Fix guest/init linkage for multilib toolchain
Quoted 1 line
Friendly ping ?
It all looks pretty self-contained, but please send another version importing the headers for v6.5 now that it has been released.
Cheers,
Will
Quoted 22 lines · On Mon, Sep 18, 2023 at 4:46?PM Will Deacon <[email protected]> wrote:
Quoted 20 lines · Anup Patel
Quoted 18 lines · On Tue, Jul 25, 2023 at 8:54?PM Anup Patel <[email protected]> wrote:
The latest KVM in Linux-6.5 has support for:
1) Svnapot ISA extension support
2) AIA in-kernel irqchip supportThis series adds corresponding changes in KVMTOOL to use the above mentioned features for Guest/VM.
These patches can also be found in the
riscv_aia_v1branch at:
https://github.com/avpatel/kvmtool.gitAnup Patel (6):
Sync-up header with Linux-6.5-rc3 for KVM RISC-V
riscv: Add Svnapot extension support
riscv: Make irqchip support pluggable
riscv: Add IRQFD support for in-kernel AIA irqchip
riscv: Use AIA in-kernel irqchip whenever KVM RISC-V supports
riscv: Fix guest/init linkage for multilib toolchain
Quoted 4 lines
Quoted 1 line
Friendly ping ?
It all looks pretty self-contained, but please send another version importing the headers for v6.5 now that it has been released.
Sure, I will send another version soon.
Thanks,
Anup