LoongArch: KVM: Implement KVM_GET/SET_SREGS for bulk CSR migration
Subsystems (3)
PATCH 1/1 LoongArch: KVM: Implement KVM_GET/SET_SREGS for bulk CSR migration
From: Tao Cui <[email protected]>
KVM_GET/SET_SREGS has so far returned -ENOIOCTLCMD with an empty struct kvm_sregs, so migrating a vCPU's CSR state takes one KVM_GET/SET_ONE_REG ioctl per register -- thousands of syscalls for a large VM.
Define struct kvm_sregs as a flat array of 0x184 entries (the core CSR range 0x0-0x183, up to DMWIN3) and implement the two ioctls:
- get_sregs does a single vcpu_load/put, which also pulls pending interrupts into ESTAT, avoiding the per-register load/put side-effect that made ONE_REG snapshots of ESTAT order-sensitive.
- set_sregs writes all CSRs via _kvm_setcsr in one pass, propagates _kvm_setcsr errors, and clears KVM_LARCH_HWCSR_USABLE up front so a mid-loop failure still forces the next vcpu_load() to reload from SW, matching KVM_SET_ONE_REG.
CSRs above 0x183 (debug, breakpoint, PMU) stay on KVM_GET/SET_ONE_REG. struct kvm_sregs was empty, so enlarging it -- and the _IOWR-derived ioctl number -- breaks no userspace; userspace built against the updated UAPI header can adopt the bulk ioctl.
On a Loongson 3A6000, snapshotting one vCPU's core CSR range drops from 388 KVM_GET_ONE_REG calls (~2 ms) to a single KVM_GET_SREGS ioctl (~5 us).
--- arch/loongarch/include/uapi/asm/kvm.h | 3 ++ arch/loongarch/kvm/vcpu.c | 43 +++++++++++++++++++++++++-- 2 files changed, 44 insertions(+), 2 deletions(-)
arch/loongarch/include/uapi/asm/kvm.h +3 -0
@@ -124,7 +124,10 @@ struct kvm_sync_regs { };/* dummy definition */ +#define KVM_LOONGARCH_NR_SREGS 0x184 +struct kvm_sregs { +__u64 csr[KVM_LOONGARCH_NR_SREGS ]; };struct kvm_iocsr_entry {
arch/loongarch/kvm/vcpu.c +41 -2
53 lines not on this page · raw message
Signature · 1 line
2.43.0
[email protected]
AI reviewThank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Critical] Redundant vcpu_load()/vcpu_put() in kvm_arch_vcpu_ioctl_get_sregs causes preempt_notifiers…
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Redundant vcpu_load()/vcpu_put() in kvm_arch_vcpu_ioctl_get_sregs causes preempt_notifiers list corruption and a guaranteed kernel crash. --
--- Patch [1]: [PATCH] LoongArch: KVM: Implement KVM_GET/SET_SREGS for bulk CSR migration --- commit 0b0da4f87cc239c49e5848ae374209644b4ea927
Author: Tao Cui <[email protected]>
LoongArch: KVM: Implement KVM_GET/SET_SREGS for bulk CSR migration
This commit adds KVM_GET_SREGS and KVM_SET_SREGS ioctls for LoongArch to allow bulk CSR migration. It defines the kvm_sregs struct as a flat array to optimize performance compared to multiple KVM_GET/SET_ONE_REG calls.
Quoted 4 lines
arch/loongarch/kvm/vcpu.c +0
-0
[ ... ]
Quoted 8 lines
arch/loongarch/kvm/vcpu.c +3
-1@@ -1001,12 +1001,51 @@ static int kvm_set_reg(struct kvm_vcpu *vcpu, const struct kvm_one_reg *reg)int kvm_arch_vcpu_ioctl_get_sregs (struct kvm_vcpu *vcpu,struct kvm_sregs *sregs) { -return -ENOIOCTLCMD ; +int i; +unsigned long estat, gintc; +struct loongarch_csrs *csr = vcpu->arch.csr;
arch/loongarch/kvm/vcpu.c static int kvm_set_reg(struct kvm_vcpu *vcpu, const struct kvm_one_reg *reg) · line 1016
Quoted 10 lines
arch/loongarch/kvm/vcpu.c +10
-0+ +/* +* Pull pending interrupts into ESTAT with a single vcpu_load/put so +* the ESTAT value read below matches the current interrupt state. +* This also avoids the per-register load/put side-effect that makes +* the ONE_REG path's ESTAT snapshot order-sensitive. The SW CSR +* reads run under vcpu->mutex, which serialises this ioctl. +*/ +preempt_disable (); +vcpu_load (vcpu);
[Severity: Critical]
Will this vcpu_load() call corrupt the preempt_notifiers hlist?
The KVM generic ioctl handler kvm_vcpu_ioctl() in virt/kvm/kvm_main.c already calls vcpu_load() before dispatching KVM_GET_SREGS. Calling vcpu_load() a second time here will double-register the preempt notifier, which calls hlist_add_head() on a node already at the head of the list, creating a circular reference.
arch/loongarch/kvm/vcpu.c static int kvm_set_reg(struct kvm_vcpu *vcpu, const struct kvm_one_reg *reg) · line 1019
Quoted 3 lines
arch/loongarch/kvm/vcpu.c +3
-0+kvm_deliver_intr (vcpu); + vcpu->arch.aux_inuse &= ~KVM_LARCH_SWCSR_LATEST ; +vcpu_put (vcpu);
[Severity: Critical]
Does this vcpu_put() cause a guaranteed kernel panic?
Because the node's pointers were corrupted by the double vcpu_load(), this vcpu_put() unregisters the node but poisons its pointers. When the ioctl returns to the generic kvm_vcpu_ioctl() handler, the outer vcpu_put() will attempt to unregister the node again. This writes to LIST_POISON2 and unconditionally triggers a fatal page fault on the host.
Quoted 3 lines
arch/loongarch/kvm/vcpu.c +3
-0+preempt_enable (); + +for (i =0 ; i <KVM_LOONGARCH_NR_SREGS ; i++) {
[ ... ]
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
Bibo Mao
maintainerQuoted 18 lines · Tao Cui
From: Tao Cui <[email protected]>
KVM_GET/SET_SREGS has so far returned
-ENOIOCTLCMDwith an empty structkvm_sregs, so migrating a vCPU's CSR state takes one KVM_GET/SET_ONE_REG ioctl per register -- thousands of syscalls for a large VM.Define struct
kvm_sregsas a flat array of0x184entries (the core CSR range 0x0-0x183, up to DMWIN3) and implement the two ioctls:-
get_sregsdoes a single vcpu_load/put, which also pulls pending interrupts into ESTAT, avoiding the per-register load/put side-effect that madeONE_REGsnapshots of ESTAT order-sensitive.
-set_sregswrites all CSRs via_kvm_setcsrin one pass, propagates_kvm_setcsrerrors, and clearsKVM_LARCH_HWCSR_USABLEup front so a mid-loop failure still forces the nextvcpu_load()to reload from SW, matchingKVM_SET_ONE_REG.
Quoted 8 lines
CSRs above
0x183(debug, breakpoint, PMU) stay on KVM_GET/SET_ONE_REG. structkvm_sregswas empty, so enlarging it -- and the _IOWR-derived ioctl number -- breaks no userspace; userspace built against the updated UAPI header can adopt the bulk ioctl.On a Loongson 3A6000, snapshotting one vCPU's core CSR range drops from 388
KVM_GET_ONE_REGcalls (~2 ms) to a singleKVM_GET_SREGSioctl (~5 us).
Great, I think getting register with bulk method is good.
Quoted 12 lines
Signed-off-by Tao Cui <[email protected]>--- arch/loongarch/include/uapi/asm/kvm.h | 3 ++ arch/loongarch/kvm/vcpu.c | 43 +++++++++++++++++++++++++-- 2 files changed, 44 insertions(+), 2 deletions(-)arch/loongarch/include/uapi/asm/kvm.h +0
-0
arch/loongarch/include/uapi/asm/kvm.h struct kvm_sync_regs { · line 130
Quoted 7 lines
arch/loongarch/include/uapi/asm/kvm.h +3
-0@@ -124,7 +124,10 @@ struct kvm_sync_regs { };/* dummy definition */ +#define KVM_LOONGARCH_NR_SREGS 0x184 +struct kvm_sregs { +__u64 csr[KVM_LOONGARCH_NR_SREGS ];
I think that get/set registers one by one is not so better. There are two possible potential problems with this method:
1. With hard-code size 0x184, there may be compatible issue, in
future there may be CSR register with index larger than 0x184
2. There may be order dependency with CSR get or set, such
timer,interrupt, or feature ctrl registers. Only that there is SW CSR shadow CSR register in KVM, so dependency relation disappears with this method.
In generic, I think KVM_GET_MSRS/KVM_SET_MSRS is a better method, VMM needs know the index and dependency at first, this API can be changed as generic and not relative with detailed architecture.
When we submit KVM to community in the beginning, this method was used, however the community suggests that new API KVM_GET_ONE_REG/KVM_SET_ONE_REG is added, it should be used. Maybe mixed of KVM_GET_BULK_REGS/KVM_GET_ONE_REG can be used :)
There is piece of UAPI with KVM_GET_MSRS/KVM_SET_MSRS.
struct kvm_msr_entry {
__u32 index;
__u32 reserved;
__u64 data;
};/* for KVM_GET_MSRS and KVM_SET_MSRS */
struct kvm_msrs {
__u32 nmsrs; /* number of msrs in entries */
__u32 pad;
__DECLARE_FLEX_ARRAY(struct kvm_msr_entry, entries);
};Regards
Bibo Mao
Quoted 61 lines
arch/loongarch/include/uapi/asm/kvm.h +0
-0};struct kvm_iocsr_entry {arch/loongarch/kvm/vcpu.c +40
-2@@ -1001,12 +1001,51 @@ static int kvm_set_reg(struct kvm_vcpu *vcpu, const struct kvm_one_reg *reg)int kvm_arch_vcpu_ioctl_get_sregs (struct kvm_vcpu *vcpu,struct kvm_sregs *sregs) { -return -ENOIOCTLCMD ; +int i; +unsigned long estat, gintc; +struct loongarch_csrs *csr = vcpu->arch.csr; + +/* +* Pull pending interrupts into ESTAT with a single vcpu_load/put so +* the ESTAT value read below matches the current interrupt state. +* This also avoids the per-register load/put side-effect that makes +* the ONE_REG path's ESTAT snapshot order-sensitive. The SW CSR +* reads run under vcpu->mutex, which serialises this ioctl. +*/ +preempt_disable (); +vcpu_load (vcpu); +kvm_deliver_intr (vcpu); + vcpu->arch.aux_inuse &= ~KVM_LARCH_SWCSR_LATEST ; +vcpu_put (vcpu); +preempt_enable (); + +for (i =0 ; i <KVM_LOONGARCH_NR_SREGS ; i++) { +if (i ==LOONGARCH_CSR_ESTAT ) { + gintc =kvm_read_sw_gcsr (csr,LOONGARCH_CSR_GINTC ) &KVM_GINTC_IRQ_MASK ; + estat =kvm_read_sw_gcsr (csr,LOONGARCH_CSR_ESTAT ) & ~KVM_ESTAT_EXTI_MASK ; + sregs->csr[i] = estat | (gintc <<VIP_DELTA ); + }else { + sregs->csr[i] = kvm_read_sw_gcsr(csr, i); > + } + } + +return 0 ; }int kvm_arch_vcpu_ioctl_set_sregs (struct kvm_vcpu *vcpu,struct kvm_sregs *sregs) { -return -ENOIOCTLCMD ; +int i, ret; + +/* Clear first so a failing _kvm_setcsr still forces a HW reload. */ + vcpu->arch.aux_inuse &= ~KVM_LARCH_HWCSR_USABLE ; + +for (i =0 ; i <KVM_LOONGARCH_NR_SREGS ; i++) { + ret =_kvm_setcsr (vcpu, i, sregs->csr[i]); +if (ret) +return ret; + } + +return 0 ; }int kvm_arch_vcpu_ioctl_get_regs (struct kvm_vcpu *vcpu,struct kvm_regs *regs)
Quoted 37 lines · Bibo Mao
Quoted 18 lines · Tao Cui
From: Tao Cui <[email protected]>
KVM_GET/SET_SREGS has so far returned
-ENOIOCTLCMDwith an empty structkvm_sregs, so migrating a vCPU's CSR state takes one KVM_GET/SET_ONE_REG ioctl per register -- thousands of syscalls for a large VM.Define struct
kvm_sregsas a flat array of0x184entries (the core CSR range 0x0-0x183, up to DMWIN3) and implement the two ioctls:-
get_sregsdoes a single vcpu_load/put, which also pulls pending interrupts into ESTAT, avoiding the per-register load/put side-effect that madeONE_REGsnapshots of ESTAT order-sensitive.
-set_sregswrites all CSRs via_kvm_setcsrin one pass, propagates_kvm_setcsrerrors, and clearsKVM_LARCH_HWCSR_USABLEup front so a mid-loop failure still forces the nextvcpu_load()to reload from SW, matchingKVM_SET_ONE_REG.Quoted 8 lines
CSRs above
0x183(debug, breakpoint, PMU) stay on KVM_GET/SET_ONE_REG. structkvm_sregswas empty, so enlarging it -- and the _IOWR-derived ioctl number -- breaks no userspace; userspace built against the updated UAPI header can adopt the bulk ioctl.On a Loongson 3A6000, snapshotting one vCPU's core CSR range drops from 388
KVM_GET_ONE_REGcalls (~2 ms) to a singleKVM_GET_SREGSioctl (~5 us).Great, I think getting register with bulk method is good.
Quoted 7 lines
Signed-off-by Tao Cui <[email protected]>---
arch/loongarch/include/uapi/asm/kvm.h| 3 ++ arch/loongarch/kvm/vcpu.c | 43 +++++++++++++++++++++++++--2 files changed, 44 insertions(+), 2 deletions(-)
Quoted 12 lines
arch/loongarch/include/uapi/asm/kvm.h struct kvm_sync_regs { · line 129
Quoted 11 lines
arch/loongarch/include/uapi/asm/kvm.h +3
-0@@ -124,7 +124,10 @@ struct kvm_sync_regs { }; /* dummy definition */ +#define KVM_LOONGARCH_NR_SREGS 0x184 + struct kvm_sregs { + __u64 csr[KVM_LOONGARCH_NR_SREGS];
Thanks for the review.
Quoted 2 lines
I think that get/set registers one by one is not so better. There are two possible potential problems with this method:
1. With hard-code size0x184, there may be compatible issue, in future there may be CSR register with index larger than0x184
On the fixed 0x184: agreed, that's a real ABI trap. I'll switch to the index+data form you suggested, like KVM_GET_MSRS:
struct kvm_loongarch_csr_entry { __u32 index; __u32 reserved; __u64 data; };
struct kvm_loongarch_csrs { __u32 ncsrs; __u32 pad;
struct kvm_loongarch_csr_entry entries[]; };One ioctl, same perf win, and new CSRs just add an index -- no ABI change.
Quoted 1 line
2. There may be order dependency with CSR get or set, such timer,interrupt, or feature ctrl registers. Only that there is SW CSR shadow CSR register in KVM, so dependency relation disappears with this method.
On ordering: the SW CSR shadow already absorbs it -- get reads kvm_read_sw_gcsr(), set writes _kvm_setcsr(), both on the SW copy, so order within one ioctl doesn't matter. get also folds pending IRQs into ESTAT via a single vcpu_load/put + kvm_deliver_intr(), and set clears KVM_LARCH_HWCSR_USABLE up front, matching KVM_SET_ONE_REG.
Quoted 3 lines
In generic, I think KVM_GET_MSRS/KVM_SET_MSRS is a better method, VMM needs know the index and dependency at first, this API can be changed as generic and not relative with detailed architecture.
A generic bulk-reg ioctl is the cleaner long-term direction, but I'd land the LoongArch-specific one first and revisit generic later.
v2 coming. Thanks again.
Thanks,
Tao
Quoted 77 lines
When we submit KVM to community in the beginning, this method was used, however the community suggests that new API KVM_GET_ONE_REG/KVM_SET_ONE_REG is added, it should be used. Maybe mixed of KVM_GET_BULK_REGS/KVM_GET_ONE_REG can be used :)
There is piece of UAPI with KVM_GET_MSRS/KVM_SET_MSRS. struct
kvm_msr_entry{
__u32index;
__u32reserved;
__u64data;
};/* for
KVM_GET_MSRSandKVM_SET_MSRS*/ structkvm_msrs{
__u32nmsrs; /* number of msrs in entries */__u32pad;
__DECLARE_FLEX_ARRAY(struct kvm_msr_entry, entries); };Regards
Bibo MaoQuoted 57 lines
arch/loongarch/include/uapi/asm/kvm.h +0
-0}; struct kvm_iocsr_entry {arch/loongarch/kvm/vcpu.c +40
-2@@ -1001,12 +1001,51 @@ static int kvm_set_reg(struct kvm_vcpu *vcpu, const struct kvm_one_reg *reg) int kvm_arch_vcpu_ioctl_get_sregs(struct kvm_vcpu *vcpu, struct kvm_sregs *sregs) { - return -ENOIOCTLCMD; + int i; + unsigned long estat, gintc; + struct loongarch_csrs *csr = vcpu->arch.csr; + + /* + * Pull pending interrupts into ESTAT with a single vcpu_load/put so + * the ESTAT value read below matches the current interrupt state. + * This also avoids the per-register load/put side-effect that makes + * the ONE_REG path's ESTAT snapshot order-sensitive. The SW CSR + * reads run under vcpu->mutex, which serialises this ioctl. + */ + preempt_disable(); + vcpu_load(vcpu); + kvm_deliver_intr(vcpu); + vcpu->arch.aux_inuse &= ~KVM_LARCH_SWCSR_LATEST; + vcpu_put(vcpu); + preempt_enable(); + + for (i = 0; i < KVM_LOONGARCH_NR_SREGS; i++) { + if (i == LOONGARCH_CSR_ESTAT) { + gintc = kvm_read_sw_gcsr(csr, LOONGARCH_CSR_GINTC) & KVM_GINTC_IRQ_MASK; + estat = kvm_read_sw_gcsr(csr, LOONGARCH_CSR_ESTAT) & ~KVM_ESTAT_EXTI_MASK; + sregs->csr[i] = estat | (gintc << VIP_DELTA); + } else { + sregs->csr[i] = kvm_read_sw_gcsr(csr, i); > + } + } + + return 0; } int kvm_arch_vcpu_ioctl_set_sregs(struct kvm_vcpu *vcpu, struct kvm_sregs *sregs) { - return -ENOIOCTLCMD; + int i, ret; + + /* Clear first so a failing _kvm_setcsr still forces a HW reload. */ + vcpu->arch.aux_inuse &= ~KVM_LARCH_HWCSR_USABLE; + + for (i = 0; i < KVM_LOONGARCH_NR_SREGS; i++) { + ret = _kvm_setcsr(vcpu, i, sregs->csr[i]); + if (ret) + return ret; + } + + return 0; } int kvm_arch_vcpu_ioctl_get_regs(struct kvm_vcpu *vcpu, struct kvm_regs *regs)