From: "Clément Léger" <cleger@rivosinc.com>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org
Subject: Re: [PATCH 3/6] RISC-V: KVM: add SBI extension init()/deinit() functions
Date: Fri, 17 Jan 2025 16:50:16 +0100 [thread overview]
Message-ID: <9fdcd0cf-334e-46f9-97c1-305f213d1ad3@rivosinc.com> (raw)
In-Reply-To: <a6196a16-808e-4a69-bcec-a83d868b726f@sifive.com>
On 11/01/2025 00:42, Samuel Holland wrote:
> Hi Clément,
>
> On 2025-01-06 9:48 AM, Clément Léger wrote:
>> The FWFT SBI extension will need to dynamically allocate memory and do
>> init time specific initialization. Add an init/deinit callbacks that
>> allows to do so.
>>
>> Signed-off-by: Clément Léger <cleger@rivosinc.com>
>> ---
>> arch/riscv/include/asm/kvm_vcpu_sbi.h | 9 ++++++++
>> arch/riscv/kvm/vcpu.c | 2 ++
>> arch/riscv/kvm/vcpu_sbi.c | 31 ++++++++++++++++++++++++++-
>> 3 files changed, 41 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/riscv/include/asm/kvm_vcpu_sbi.h b/arch/riscv/include/asm/kvm_vcpu_sbi.h
>> index b96705258cf9..8c465ce90e73 100644
>> --- a/arch/riscv/include/asm/kvm_vcpu_sbi.h
>> +++ b/arch/riscv/include/asm/kvm_vcpu_sbi.h
>> @@ -49,6 +49,14 @@ struct kvm_vcpu_sbi_extension {
>>
>> /* Extension specific probe function */
>> unsigned long (*probe)(struct kvm_vcpu *vcpu);
>> +
>> + /*
>> + * Init/deinit function called once during VCPU init/destroy. These
>> + * might be use if the SBI extensions need to allocate or do specific
>> + * init time only configuration.
>> + */
>> + int (*init)(struct kvm_vcpu *vcpu);
>> + void (*deinit)(struct kvm_vcpu *vcpu);
>> };
>>
>> void kvm_riscv_vcpu_sbi_forward(struct kvm_vcpu *vcpu, struct kvm_run *run);
>> @@ -69,6 +77,7 @@ const struct kvm_vcpu_sbi_extension *kvm_vcpu_sbi_find_ext(
>> bool riscv_vcpu_supports_sbi_ext(struct kvm_vcpu *vcpu, int idx);
>> int kvm_riscv_vcpu_sbi_ecall(struct kvm_vcpu *vcpu, struct kvm_run *run);
>> void kvm_riscv_vcpu_sbi_init(struct kvm_vcpu *vcpu);
>> +void kvm_riscv_vcpu_sbi_deinit(struct kvm_vcpu *vcpu);
>>
>> int kvm_riscv_vcpu_get_reg_sbi_sta(struct kvm_vcpu *vcpu, unsigned long reg_num,
>> unsigned long *reg_val);
>> diff --git a/arch/riscv/kvm/vcpu.c b/arch/riscv/kvm/vcpu.c
>> index e048dcc6e65e..3420a4a62c94 100644
>> --- a/arch/riscv/kvm/vcpu.c
>> +++ b/arch/riscv/kvm/vcpu.c
>> @@ -180,6 +180,8 @@ void kvm_arch_vcpu_postcreate(struct kvm_vcpu *vcpu)
>>
>> void kvm_arch_vcpu_destroy(struct kvm_vcpu *vcpu)
>> {
>> + kvm_riscv_vcpu_sbi_deinit(vcpu);
>> +
>> /* Cleanup VCPU AIA context */
>> kvm_riscv_vcpu_aia_deinit(vcpu);
>>
>> diff --git a/arch/riscv/kvm/vcpu_sbi.c b/arch/riscv/kvm/vcpu_sbi.c
>> index 6e704ed86a83..d2dbb0762072 100644
>> --- a/arch/riscv/kvm/vcpu_sbi.c
>> +++ b/arch/riscv/kvm/vcpu_sbi.c
>> @@ -486,7 +486,7 @@ void kvm_riscv_vcpu_sbi_init(struct kvm_vcpu *vcpu)
>> struct kvm_vcpu_sbi_context *scontext = &vcpu->arch.sbi_context;
>> const struct kvm_riscv_sbi_extension_entry *entry;
>> const struct kvm_vcpu_sbi_extension *ext;
>> - int idx, i;
>> + int idx, i, ret;
>>
>> for (i = 0; i < ARRAY_SIZE(sbi_ext); i++) {
>> entry = &sbi_ext[i];
>> @@ -501,8 +501,37 @@ void kvm_riscv_vcpu_sbi_init(struct kvm_vcpu *vcpu)
>> continue;
>> }
>>
>> + if (ext->init) {
>> + ret = ext->init(vcpu);
>> + if (ret)
>> + scontext->ext_status[idx] =
>> + KVM_RISCV_SBI_EXT_STATUS_UNAVAILABLE;
>> + }
>> +
>> scontext->ext_status[idx] = ext->default_disabled ?
>> KVM_RISCV_SBI_EXT_STATUS_DISABLED :
>> KVM_RISCV_SBI_EXT_STATUS_ENABLED;
>
> This will overwrite the KVM_RISCV_SBI_EXT_STATUS_UNAVAILABLE set above.
Oh yes indeed, I should add a "continue" under the if above.
>
>> }
>> }
>> +
>> +void kvm_riscv_vcpu_sbi_deinit(struct kvm_vcpu *vcpu)
>> +{
>> + struct kvm_vcpu_sbi_context *scontext = &vcpu->arch.sbi_context;
>> + const struct kvm_riscv_sbi_extension_entry *entry;
>> + const struct kvm_vcpu_sbi_extension *ext;
>> + int idx, i;
>> +
>> + for (i = 0; i < ARRAY_SIZE(sbi_ext); i++) {
>> + entry = &sbi_ext[i];
>> + ext = entry->ext_ptr;
>> + idx = entry->ext_idx;
>> +
>> + if (idx < 0 || idx >= ARRAY_SIZE(scontext->ext_status))
>> + continue;
>> +
>> + if (scontext->ext_status[idx] != KVM_RISCV_SBI_EXT_STATUS_ENABLED || !ext->deinit)
>
> Given that an extension can be enabled/disabled after initialization, this
> should only skip deinit if the status is UNAVAILABLE.
yeah, make sense as well,
Thanks for the review,
Clément
>
> Regards,
> Samuel
>
>> + continue;
>> +
>> + ext->deinit(vcpu);
>> + }
>> +}
>
next prev parent reply other threads:[~2025-01-17 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 15:48 [PATCH 0/6] riscv: add SBI FWFT misaligned exception delegation support Clément Léger
2025-01-06 15:48 ` [PATCH 1/6] riscv: add Firmware Feature (FWFT) SBI extensions definitions Clément Léger
2025-01-10 23:24 ` Samuel Holland
2025-01-06 15:48 ` [PATCH 2/6] riscv: request misaligned exception delegation from SBI Clément Léger
2025-01-07 3:28 ` Jesse T
2025-01-10 23:35 ` Samuel Holland
2025-01-17 15:09 ` Clément Léger
2025-01-06 15:48 ` [PATCH 3/6] RISC-V: KVM: add SBI extension init()/deinit() functions Clément Léger
2025-01-10 23:42 ` Samuel Holland
2025-01-17 15:50 ` Clément Léger [this message]
2025-01-06 15:48 ` [PATCH 4/6] RISC-V: KVM: add support for FWFT SBI extension Clément Léger
2025-01-10 23:47 ` Samuel Holland
2025-01-06 15:48 ` [PATCH 5/6] riscv: export unaligned_ctl_available() as a GPL symbol Clément Léger
2025-01-07 3:34 ` Jesse T
2025-01-06 15:48 ` [PATCH 6/6] RISC-V: KVM: add support for SBI_FWFT_MISALIGNED_DELEG Clément Léger
2025-01-10 23:55 ` Samuel Holland
2025-01-17 16:05 ` Clément Léger
2025-01-17 16:31 ` Samuel Holland
2025-01-20 8:25 ` Clément Léger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9fdcd0cf-334e-46f9-97c1-305f213d1ad3@rivosinc.com \
--to=cleger@rivosinc.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®