[PATCH v3 4/4] RISC-V: KVM: Mark the reset callback of FWFT extension always dirties CSR
Inochi Amaoto
inochiama at gmail.com
Wed Jul 29 16:25:25 PDT 2026
As the CSR is only flushed when the csr_dirty is set, always set the
csr_dirty field in kvm_sbi_ext_fwft_reset() so the CSR change can take
effect immediately. This unconditional set should be safe as all
supported FWFT features change the CSR state currently.
Signed-off-by: Inochi Amaoto <inochiama at gmail.com>
---
arch/riscv/kvm/vcpu_sbi_fwft.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/riscv/kvm/vcpu_sbi_fwft.c b/arch/riscv/kvm/vcpu_sbi_fwft.c
index 56fb59afe02a..2e35e7e12327 100644
--- a/arch/riscv/kvm/vcpu_sbi_fwft.c
+++ b/arch/riscv/kvm/vcpu_sbi_fwft.c
@@ -601,6 +601,8 @@ static void kvm_sbi_ext_fwft_reset(struct kvm_vcpu *vcpu)
if (feature->reset)
feature->reset(vcpu);
}
+
+ vcpu->arch.csr_dirty = true;
}
static void kvm_sbi_ext_fwft_validate(struct kvm_vcpu *vcpu)
--
2.55.0
More information about the linux-riscv
mailing list