[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DCTJ9US6E4PG.1MA4ICDR21DS6@ventanamicro.com>
Date: Mon, 15 Sep 2025 19:01:03 +0200
From: Radim Krčmář <rkrcmar@...tanamicro.com>
To: "Jinyu Tang" <tjytimi@....com>, "Anup Patel" <anup@...infault.org>,
"Atish Patra" <atish.patra@...ux.dev>, "Andrew Jones"
<ajones@...tanamicro.com>, "Conor Dooley" <conor.dooley@...rochip.com>,
"Yong-Xuan Wang" <yongxuan.wang@...ive.com>, "Paul Walmsley"
<paul.walmsley@...ive.com>, "Nutty Liu" <nutty.liu@...mail.com>
Cc: <kvm@...r.kernel.org>, <kvm-riscv@...ts.infradead.org>,
<linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
"Tianshun Sun" <stsmail163@....com>
Subject: Re: [RFC PATCH] kvm/riscv: Add ctxsstatus and ctxhstatus for
migration
2025-09-15T18:52:56+02:00, Radim Krčmář <rkrcmar@...tanamicro.com>:
> 2025-09-15T23:27:31+08:00, Jinyu Tang <tjytimi@....com>:
>> + if (reg_num == KVM_REG_RISCV_CSR_REG(ctxhstatus))
>> + csr->ctxhstatus = vcpu->arch.guest_context.hstatus;
>
> Neither should userspace be able to directly set hstatus.
> KVM should derive it from other userspace configuration.
>
> What isn't correctly reflected in hstatus?
Ah, we don't set hstatus.SPVP when setting KVM_REG_RISCV_CORE_REG(mode).
Powered by blists - more mailing lists