KVMTOOL RISC-V Svpbmt and Sstc Support
Subsystems (5)
cover KVMTOOL RISC-V Svpbmt and Sstc Support
The latest Linux-6.0-rc1 has support for Svpbmt and Sstc extensions in KVM RISC-V. This series adds corresponding changes in KVMTOOL to allow Guest/VM use these new RISC-V extensions.
The PATCH5 is an unrelated fix which was discovered while developing this series.
These patches can also be found in the riscv_svpbmt_sstc_v1 branch
at: https://github.com/avpatel/kvmtool.git
Anup Patel (3):
Update UAPI headers based on Linux-6.0-rc1
riscv: Add Svpbmt extension support
riscv: Fix serial0 alias path
Atish Patra (2):
riscv: Append ISA extensions to the device tree
riscv: Add Sstc extension support
arm/aarch64/include/asm/kvm.h | 36 ++++++ include/linux/kvm.h | 181 +++++++++++++++++++++++++++++-- include/linux/virtio_9p.h | 2 +- include/linux/virtio_config.h | 7 +- include/linux/virtio_ids.h | 14 +-- include/linux/virtio_net.h | 34 +++++- include/linux/virtio_pci.h | 2 + riscv/fdt.c | 44 +++++++- riscv/include/asm/kvm.h | 22 ++++ riscv/include/kvm/kvm-cpu-arch.h | 11 ++ riscv/kvm-cpu.c | 11 -- x86/include/asm/kvm.h | 33 +++--- 12 files changed, 352 insertions(+), 45 deletions(-)
Signature · 1 line
2.34.1
PATCH 1/5 Update UAPI headers based on Linux-6.0-rc1
We update all UAPI headers based on Linux-6.0-rc1 so that we can use latest features.
--- arm/aarch64/include/asm/kvm.h | 36 +++++++ include/linux/kvm.h | 181 ++++++++++++++++++++++++++++++++-- include/linux/virtio_9p.h | 2 +- include/linux/virtio_config.h | 7 +- include/linux/virtio_ids.h | 14 +-- include/linux/virtio_net.h | 34 ++++++- include/linux/virtio_pci.h | 2 + riscv/include/asm/kvm.h | 22 +++++ x86/include/asm/kvm.h | 33 ++++--- 9 files changed, 301 insertions(+), 30 deletions(-)
arm/aarch64/include/asm/kvm.h +36 -0
@@ -139,8 +139,10 @@ struct kvm_guest_debug_arch {__u64 dbg_wvr[KVM_ARM_MAX_DBG_REGS ]; }; +#define KVM_DEBUG_ARCH_HSR_HIGH_VALID (1 << 0)struct kvm_debug_exit_arch {__u32 hsr; +__u32 hsr_high;/* ESR_EL2[61:32] */ __u64 far;/* used for watchpoints */ };
@@ -332,6 +334,40 @@ struct kvm_arm_copy_mte_tags {#define KVM_ARM64_SVE_VLS_WORDS \ ((KVM_ARM64_SVE_VQ_MAX - KVM_ARM64_SVE_VQ_MIN) / 64 + 1) +/* Bitmap feature firmware registers */ +#define KVM_REG_ARM_FW_FEAT_BMAP (0x0016 << KVM_REG_ARM_COPROC_SHIFT) +#define KVM_REG_ARM_FW_FEAT_BMAP_REG (r) (KVM_REG_ARM64 | KVM_REG_SIZE_U64 | \ + KVM_REG_ARM_FW_FEAT_BMAP | \ + ((r) & 0xffff)) + +#define KVM_REG_ARM_STD_BMAP KVM_REG_ARM_FW_FEAT_BMAP_REG(0) + +enum { +KVM_REG_ARM_STD_BIT_TRNG_V1_0 =0 , +#ifdef __KERNEL__ +KVM_REG_ARM_STD_BMAP_BIT_COUNT , +#endif +}; + +#define KVM_REG_ARM_STD_HYP_BMAP KVM_REG_ARM_FW_FEAT_BMAP_REG(1) + +enum { +KVM_REG_ARM_STD_HYP_BIT_PV_TIME =0 , +#ifdef __KERNEL__ +KVM_REG_ARM_STD_HYP_BMAP_BIT_COUNT , +#endif +}; + +#define KVM_REG_ARM_VENDOR_HYP_BMAP KVM_REG_ARM_FW_FEAT_BMAP_REG(2) + +enum { +KVM_REG_ARM_VENDOR_HYP_BIT_FUNC_FEAT =0 , +KVM_REG_ARM_VENDOR_HYP_BIT_PTP =1 , +#ifdef __KERNEL__ +KVM_REG_ARM_VENDOR_HYP_BMAP_BIT_COUNT , +#endif +}; +/* Device Control API: ARM VGIC */ #define KVM_DEV_ARM_VGIC_GRP_ADDR 0#define KVM_DEV_ARM_VGIC_GRP_DIST_REGS 1
include/linux/kvm.h +174 -7
299 lines not on this page · raw message
include/linux/virtio_9p.h +1 -1
@@ -38,7 +38,7 @@ struct virtio_9p_config {/* length of the tag name */ __virtio16 tag_len;/* non-NULL terminated tag name */ -__u8 tag[0 ]; +__u8 tag[]; } __attribute__((packed));#endif /* _LINUX_VIRTIO_9P_H */
include/linux/virtio_config.h +6 -1
@@ -52,7 +52,7 @@* rest are per-device feature bits. */ #define VIRTIO_TRANSPORT_F_START 28 -#define VIRTIO_TRANSPORT_F_END 38 +#define VIRTIO_TRANSPORT_F_END 41#ifndef VIRTIO_CONFIG_NO_LEGACY /* Do we get callbacks when the ring is completely used, even if we've
@@ -98,4 +98,9 @@* Does the device support Single Root I/O Virtualization? */ #define VIRTIO_F_SR_IOV 37 + +/* +* This feature indicates that the driver can reset a queue individually. +*/ +#define VIRTIO_F_RING_RESET 40#endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */
include/linux/virtio_ids.h +7 -7
@@ -73,12 +73,12 @@* Virtio Transitional IDs */ -#define VIRTIO_TRANS_ID_NET 1000/* transitional virtio net */ -#define VIRTIO_TRANS_ID_BLOCK 1001/* transitional virtio block */ -#define VIRTIO_TRANS_ID_BALLOON 1002/* transitional virtio balloon */ -#define VIRTIO_TRANS_ID_CONSOLE 1003/* transitional virtio console */ -#define VIRTIO_TRANS_ID_SCSI 1004/* transitional virtio SCSI */ -#define VIRTIO_TRANS_ID_RNG 1005/* transitional virtio rng */ -#define VIRTIO_TRANS_ID_9P 1009/* transitional virtio 9p console */ +#define VIRTIO_TRANS_ID_NET 0x1000/* transitional virtio net */ +#define VIRTIO_TRANS_ID_BLOCK 0x1001/* transitional virtio block */ +#define VIRTIO_TRANS_ID_BALLOON 0x1002/* transitional virtio balloon */ +#define VIRTIO_TRANS_ID_CONSOLE 0x1003/* transitional virtio console */ +#define VIRTIO_TRANS_ID_SCSI 0x1004/* transitional virtio SCSI */ +#define VIRTIO_TRANS_ID_RNG 0x1005/* transitional virtio rng */ +#define VIRTIO_TRANS_ID_9P 0x1009/* transitional virtio 9p console */ #endif /* _LINUX_VIRTIO_IDS_H */
include/linux/virtio_net.h +33 -1
@@ -56,7 +56,7 @@#define VIRTIO_NET_F_MQ 22/* Device supports Receive Flow * Steering */ #define VIRTIO_NET_F_CTRL_MAC_ADDR 23/* Set MAC address */ - +#define VIRTIO_NET_F_NOTF_COAL 53/* Guest can handle notifications coalescing */ #define VIRTIO_NET_F_HASH_REPORT 57/* Supports hash report */ #define VIRTIO_NET_F_RSS 60/* Supports RSS RX steering */ #define VIRTIO_NET_F_RSC_EXT 61/* extended coalescing info */
@@ -355,4 +355,36 @@ struct virtio_net_hash_config {#define VIRTIO_NET_CTRL_GUEST_OFFLOADS 5#define VIRTIO_NET_CTRL_GUEST_OFFLOADS_SET 0 +/* +* Control notifications coalescing. +* +* Request the device to change the notifications coalescing parameters. +* +* Available with the VIRTIO_NET_F_NOTF_COAL feature bit. +*/ +#define VIRTIO_NET_CTRL_NOTF_COAL 6 +/* +* Set the tx-usecs/tx-max-packets patameters. +* tx-usecs - Maximum number of usecs to delay a TX notification. +* tx-max-packets - Maximum number of packets to send before a TX notification. +*/ +struct virtio_net_ctrl_coal_tx { +__le32 tx_max_packets; +__le32 tx_usecs; +}; + +#define VIRTIO_NET_CTRL_NOTF_COAL_TX_SET 0 + +/* +* Set the rx-usecs/rx-max-packets patameters. +* rx-usecs - Maximum number of usecs to delay a RX notification. +* rx-max-frames - Maximum number of packets to receive before a RX notification. +*/ +struct virtio_net_ctrl_coal_rx { +__le32 rx_max_packets; +__le32 rx_usecs; +}; + +#define VIRTIO_NET_CTRL_NOTF_COAL_RX_SET 1 +#endif /* _UAPI_LINUX_VIRTIO_NET_H */
include/linux/virtio_pci.h +2 -0
@@ -202,6 +202,8 @@ struct virtio_pci_cfg_cap {#define VIRTIO_PCI_COMMON_Q_AVAILHI 44#define VIRTIO_PCI_COMMON_Q_USEDLO 48#define VIRTIO_PCI_COMMON_Q_USEDHI 52 +#define VIRTIO_PCI_COMMON_Q_NDATA 56 +#define VIRTIO_PCI_COMMON_Q_RESET 58#endif /* VIRTIO_PCI_NO_MODERN */
riscv/include/asm/kvm.h +22 -0
@@ -82,6 +82,25 @@ struct kvm_riscv_timer {__u64 state; }; +/* +* ISA extension IDs specific to KVM. This is not the same as the host ISA +* extension IDs as that is internal to the host and should not be exposed +* to the guest. This should always be contiguous to keep the mapping simple +* in KVM implementation. +*/ +enum KVM_RISCV_ISA_EXT_ID { +KVM_RISCV_ISA_EXT_A =0 , +KVM_RISCV_ISA_EXT_C , +KVM_RISCV_ISA_EXT_D , +KVM_RISCV_ISA_EXT_F , +KVM_RISCV_ISA_EXT_H , +KVM_RISCV_ISA_EXT_I , +KVM_RISCV_ISA_EXT_M , +KVM_RISCV_ISA_EXT_SVPBMT , +KVM_RISCV_ISA_EXT_SSTC , +KVM_RISCV_ISA_EXT_MAX , +}; +/* Possible states for kvm_riscv_timer */ #define KVM_RISCV_TIMER_STATE_OFF 0#define KVM_RISCV_TIMER_STATE_ON 1
@@ -123,6 +142,9 @@ struct kvm_riscv_timer {#define KVM_REG_RISCV_FP_D_REG (name) \ (offsetof(struct __riscv_d_ext_state, name) / sizeof(__u64)) +/* ISA Extension registers are mapped as type 7 */ +#define KVM_REG_RISCV_ISA_EXT (0x07 << KVM_REG_RISCV_TYPE_SHIFT) +#endif #endif /* __LINUX_KVM_RISCV_H */
x86/include/asm/kvm.h +20 -13
@@ -198,13 +198,13 @@ struct kvm_msrs {__u32 nmsrs;/* number of msrs in entries */ __u32 pad; -struct kvm_msr_entry entries[0 ]; +struct kvm_msr_entry entries[]; };/* for KVM_GET_MSR_INDEX_LIST */ struct kvm_msr_list {__u32 nmsrs;/* number of msrs in entries */ -__u32 indices[0 ]; +__u32 indices[]; };/* Maximum size of any access bitmap in bytes */
@@ -241,7 +241,7 @@ struct kvm_cpuid_entry {struct kvm_cpuid {__u32 nent;__u32 padding; -struct kvm_cpuid_entry entries[0 ]; +struct kvm_cpuid_entry entries[]; };struct kvm_cpuid_entry2 {
@@ -263,7 +263,7 @@ struct kvm_cpuid_entry2 {struct kvm_cpuid2 {__u32 nent;__u32 padding; -struct kvm_cpuid_entry2 entries[0 ]; +struct kvm_cpuid_entry2 entries[]; };/* for KVM_GET_PIT and KVM_SET_PIT */
@@ -306,7 +306,8 @@ struct kvm_pit_state {struct kvm_pit_channel_state channels[3 ]; }; -#define KVM_PIT_FLAGS_HPET_LEGACY 0x00000001 +#define KVM_PIT_FLAGS_HPET_LEGACY 0x00000001 +#define KVM_PIT_FLAGS_SPEAKER_DATA_ON 0x00000002struct kvm_pit_state2 {struct kvm_pit_channel_state channels[3 ];
@@ -325,6 +326,7 @@ struct kvm_reinject_control {#define KVM_VCPUEVENT_VALID_SHADOW 0x00000004#define KVM_VCPUEVENT_VALID_SMM 0x00000008#define KVM_VCPUEVENT_VALID_PAYLOAD 0x00000010 +#define KVM_VCPUEVENT_VALID_TRIPLE_FAULT 0x00000020/* Interrupt shadow states */ #define KVM_X86_SHADOW_INT_MOV_SS 0x01
@@ -359,7 +361,10 @@ struct kvm_vcpu_events {__u8 smm_inside_nmi;__u8 latched_init; } smi; -__u8 reserved[27 ]; +struct { +__u8 pending; + } triple_fault; +__u8 reserved[26 ];__u8 exception_has_payload;__u64 exception_payload; };
@@ -389,7 +394,7 @@ struct kvm_xsave {* the contents of CPUID leaf 0xD on the host. */ __u32 region[1024 ]; -__u32 extra[0 ]; +__u32 extra[]; };#define KVM_MAX_XCRS 16
@@ -428,11 +433,13 @@ struct kvm_sync_regs {struct kvm_vcpu_events events; }; -#define KVM_X86_QUIRK_LINT0_REENABLED (1 << 0) -#define KVM_X86_QUIRK_CD_NW_CLEARED (1 << 1) -#define KVM_X86_QUIRK_LAPIC_MMIO_HOLE (1 << 2) -#define KVM_X86_QUIRK_OUT_7E_INC_RIP (1 << 3) -#define KVM_X86_QUIRK_MISC_ENABLE_NO_MWAIT (1 << 4) +#define KVM_X86_QUIRK_LINT0_REENABLED (1 << 0) +#define KVM_X86_QUIRK_CD_NW_CLEARED (1 << 1) +#define KVM_X86_QUIRK_LAPIC_MMIO_HOLE (1 << 2) +#define KVM_X86_QUIRK_OUT_7E_INC_RIP (1 << 3) +#define KVM_X86_QUIRK_MISC_ENABLE_NO_MWAIT (1 << 4) +#define KVM_X86_QUIRK_FIX_HYPERCALL_INSN (1 << 5) +#define KVM_X86_QUIRK_MWAIT_NEVER_UD_FAULTS (1 << 6)#define KVM_STATE_NESTED_FORMAT_VMX 0#define KVM_STATE_NESTED_FORMAT_SVM 1
@@ -515,7 +522,7 @@ struct kvm_pmu_event_filter {__u32 fixed_counter_bitmap;__u32 flags;__u32 pad[4 ]; -__u64 events[0 ]; +__u64 events[]; };#define KVM_PMU_EVENT_ALLOW 0
Signature · 1 line
2.34.1
PATCH 2/5 riscv: Append ISA extensions to the device tree
In reply to Anup PatelFrom: Atish Patra <[email protected]>
The riscv,isa DT property only contains single letter base extensions until now. However, there are also multi-letter extensions which were ratified recently. Add a mechanism to append those extension details to the device tree so that guest can leverage those.
--- riscv/fdt.c | 30 ++++++++++++++++++++++++++++++ riscv/include/kvm/kvm-cpu-arch.h | 11 +++++++++++ riscv/kvm-cpu.c | 11 ----------- 3 files changed, 41 insertions(+), 11 deletions(-)
riscv/fdt.c +30 -0
@@ -9,6 +9,16 @@#include <linux/kernel.h> #include <linux/sizes.h> +#define RISCV_ISA_EXT_REG (id) __kvm_reg_id(KVM_REG_RISCV_ISA_EXT, \ + id, KVM_REG_SIZE_ULONG) +struct isa_ext_info { +const char *name; +unsigned long ext_id; +}; + +struct isa_ext_info isa_info_arr[] = { +}; +static void dump_fdt (const char *dtb_file,void *fdt) {int count, fd;
@@ -31,6 +41,7 @@ static void generate_cpu_nodes(void *fdt, struct kvm *kvm) {int cpu, pos, i, index, valid_isa_len;const char *valid_isa_order ="IEMAFDQCLBJTPVNSUHKORWXYZG" ; +int arr_sz =ARRAY_SIZE (isa_info_arr);_FDT (fdt_begin_node (fdt,"cpus" ));_FDT (fdt_property_cell (fdt,"#address-cells" ,0x1 ));
@@ -42,6 +53,8 @@ static void generate_cpu_nodes(void *fdt, struct kvm *kvm)char cpu_name[CPU_NAME_MAX_LEN ];char cpu_isa[CPU_ISA_MAX_LEN ];struct kvm_cpu *vcpu = kvm->cpus[cpu]; +struct kvm_one_reg reg; +unsigned long isa_ext_out =0 ;snprintf (cpu_name,CPU_NAME_MAX_LEN ,"cpu@%x" , cpu);
@@ -53,6 +66,23 @@ static void generate_cpu_nodes(void *fdt, struct kvm *kvm)if (vcpu->riscv_isa & (1 << (index))) cpu_isa[pos++] ='a' + index; } + +for (i =0 ; i < arr_sz; i++) { + reg.id =RISCV_ISA_EXT_REG (isa_info_arr[i].ext_id); + reg.addr = (unsigned long )&isa_ext_out; +if (ioctl (vcpu->vcpu_fd,KVM_GET_ONE_REG , ®) <0 ) +continue ; +if (!isa_ext_out) +/* This extension is not available in hardware */ +continue ; + +if ((strlen (isa_info_arr[i].name) + pos +1 ) >=CPU_ISA_MAX_LEN ) { +pr_warning ("Insufficient space to append ISA exension\n" ); +break ; + } + pos +=snprintf (cpu_isa + pos,CPU_ISA_MAX_LEN ,"_%s" , + isa_info_arr[i].name); + } cpu_isa[pos] ='\0' ;_FDT (fdt_begin_node (fdt, cpu_name));
riscv/include/kvm/kvm-cpu-arch.h +11 -0
@@ -7,6 +7,17 @@#include "kvm/kvm.h" +static inline __u64 __kvm_reg_id (__u64 type,__u64 idx,__u64 size) +{ +return KVM_REG_RISCV | type | idx | size; +} + +#if __riscv_xlen ==64 +#define KVM_REG_SIZE_ULONG KVM_REG_SIZE_U64 +#else +#define KVM_REG_SIZE_ULONG KVM_REG_SIZE_U32 +#endif +struct kvm_cpu {pthread_t thread;
riscv/kvm-cpu.c +0 -11
@@ -18,17 +18,6 @@ int kvm_cpu__get_debug_fd(void)return debug_fd; } -static __u64 __kvm_reg_id (__u64 type,__u64 idx,__u64 size) -{ -return KVM_REG_RISCV | type | idx | size; -} - -#if __riscv_xlen ==64 -#define KVM_REG_SIZE_ULONG KVM_REG_SIZE_U64 -#else -#define KVM_REG_SIZE_ULONG KVM_REG_SIZE_U32 -#endif -#define RISCV_CONFIG_REG (name) __kvm_reg_id(KVM_REG_RISCV_CONFIG, \ KVM_REG_RISCV_CONFIG_REG(name), \ KVM_REG_SIZE_ULONG)
Signature · 1 line
2.34.1
PATCH 3/5 riscv: Add Svpbmt extension support
In reply to Anup PatelThe Svpbmt extension allows PTE based memory attributes in page tables. This extension also allows Guest/VM to use PTE based memory attributes in VS-stage page tables so let us add it Guest/VM ISA string when KVM RISC-V supports it.
--- riscv/fdt.c | 1 + 1 file changed, 1 insertion(+)
riscv/fdt.c +1 -0
@@ -17,6 +17,7 @@ struct isa_ext_info { };struct isa_ext_info isa_info_arr[] = { + {"svpbmt" ,KVM_RISCV_ISA_EXT_SVPBMT }, };static void dump_fdt (const char *dtb_file,void *fdt)
Signature · 1 line
2.34.1
PATCH 4/5 riscv: Add Sstc extension support
In reply to Anup PatelFrom: Atish Patra <[email protected]>
Sstc extension allows the guest OS to program the timer directly without relying on the SBI call. The kernel detects the presence of Sstc extnesion from the riscv,isa DT property. Add the Sstc extension to the device tree if it is supported by the host.
--- riscv/fdt.c | 1 + 1 file changed, 1 insertion(+)
riscv/fdt.c +1 -0
@@ -18,6 +18,7 @@ struct isa_ext_info {struct isa_ext_info isa_info_arr[] = { {"svpbmt" ,KVM_RISCV_ISA_EXT_SVPBMT }, + {"sstc" ,KVM_RISCV_ISA_EXT_SSTC }, };static void dump_fdt (const char *dtb_file,void *fdt)
Signature · 1 line
2.34.1
PATCH 5/5 riscv: Fix serial0 alias path
In reply to Anup PatelWe have all MMIO devices under "/smb" DT node so the serial0 alias path should have "/smb" prefix.
--- riscv/fdt.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
riscv/fdt.c +8 -4
@@ -122,6 +122,7 @@ static int setup_fdt(struct kvm *kvm)cpu_to_fdt64 (kvm->arch.memory_guest_start), cpu_to_fdt64(kvm->ram_size), }; +char *str;void *fdt = staging_fdt;void *fdt_dest =guest_flat_to_host (kvm, kvm->arch.dtb_guest_start);
@@ -205,12 +206,15 @@ static int setup_fdt(struct kvm *kvm)_FDT (fdt_end_node (fdt));if (fdt_stdout_path) { -_FDT (fdt_begin_node (fdt,"aliases" )); -_FDT (fdt_property_string (fdt,"serial0" , fdt_stdout_path)); -_FDT (fdt_end_node (fdt)); - + str =malloc (strlen (fdt_stdout_path) +strlen ("/smb" ) +1 ); +sprintf (str,"/smb%s" , fdt_stdout_path);free (fdt_stdout_path); fdt_stdout_path =NULL ; + +_FDT (fdt_begin_node (fdt,"aliases" )); +_FDT (fdt_property_string (fdt,"serial0" , str)); +_FDT (fdt_end_node (fdt)); +free (str); }/* Finalise. */
Signature · 1 line
2.34.1
Anup Patel
maintainerHi Will,
Quoted 34 lines · Anup Patel
The latest Linux-6.0-rc1 has support for Svpbmt and Sstc extensions in KVM RISC-V. This series adds corresponding changes in KVMTOOL to allow Guest/VM use these new RISC-V extensions.
The PATCH5 is an unrelated fix which was discovered while developing this series.
These patches can also be found in the
riscv_svpbmt_sstc_v1branch
at: https://github.com/avpatel/kvmtool.gitAnup Patel (3):
Update UAPI headers based on Linux-6.0-rc1
riscv: Add Svpbmt extension support
riscv: Fix serial0 alias pathAtish Patra (2):
riscv: Append ISA extensions to the device tree
riscv: Add Sstc extension supportarm/aarch64/include/asm/kvm.h | 36 ++++++ include/linux/kvm.h | 181 +++++++++++++++++++++++++++++-- include/linux/virtio_9p.h | 2 +- include/linux/virtio_config.h | 7 +- include/linux/virtio_ids.h | 14 +-- include/linux/virtio_net.h | 34 +++++- include/linux/virtio_pci.h | 2 + riscv/fdt.c | 44 +++++++- riscv/include/asm/kvm.h | 22 ++++ riscv/include/kvm/kvm-cpu-arch.h | 11 ++ riscv/kvm-cpu.c | 11 -- x86/include/asm/kvm.h | 33 +++--- 12 files changed, 352 insertions(+), 45 deletions(-)
Quoted 3 lines
--
2.34.1
Ping ?
Does this series look fine to you ?
Regards,
Anup
Will Deacon
AppliedQuoted 8 lines · Anup Patel
The latest Linux-6.0-rc1 has support for Svpbmt and Sstc extensions in KVM RISC-V. This series adds corresponding changes in KVMTOOL to allow Guest/VM use these new RISC-V extensions.
The PATCH5 is an unrelated fix which was discovered while developing this series.
[...]
Applied to kvmtool (master), thanks!
[1/5] Update UAPI headers based on Linux-6.0-rc1
https://git.kernel.org/will/kvmtool/c/8d0facec06ae [2/5] riscv: Append ISA extensions to the device tree https://git.kernel.org/will/kvmtool/c/8aff29e1dafe [3/5] riscv: Add Svpbmt extension support https://git.kernel.org/will/kvmtool/c/2b4fe0f8cff1 [4/5] riscv: Add Sstc extension support https://git.kernel.org/will/kvmtool/c/3c07aeaf993a [5/5] riscv: Fix serial0 alias path https://git.kernel.org/will/kvmtool/c/ed805be52f57
Cheers,
Signature · 5 lines
Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev