From: fangyu.yu@linux.alibaba.com
To: anup@brainfault.org
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, atish.patra@linux.dev,
fangyu.yu@linux.alibaba.com, graf@amazon.com, guoren@kernel.org,
jiangyifei@huawei.com, kvm-riscv@lists.infradead.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, pbonzini@redhat.com
Subject: Re: Re: [PATCH] RISC-V: KVM: Fix guest page fault within HLV* instructions
Date: Thu, 6 Nov 2025 21:29:50 +0800 [thread overview]
Message-ID: <20251106132950.80534-1-fangyu.yu@linux.alibaba.com> (raw)
In-Reply-To: <CAAhSdy0azfC-L3buko7-mN1PDWxi08HN=3NQ+0VeyMR8gVJNoQ@mail.gmail.com>
>> From: Fangyu Yu <fangyu.yu@linux.alibaba.com>
>>
>> When executing HLV* instructions at the HS mode, a guest page fault
>> may occur when a g-stage page table migration between triggering the
>> virtual instruction exception and executing the HLV* instruction.
>>
>> This may be a corner case, and one simpler way to handle this is to
>> re-execute the instruction where the virtual instruction exception
>> occurred, and the guest page fault will be automatically handled.
>>
>> Fixes: 9f7013265112 ("RISC-V: KVM: Handle MMIO exits for VCPU")
>> Signed-off-by: Fangyu Yu <fangyu.yu@linux.alibaba.com>
>> ---
>> arch/riscv/kvm/vcpu_insn.c | 21 ++++++++++++++++++---
>> 1 file changed, 18 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/riscv/kvm/vcpu_insn.c b/arch/riscv/kvm/vcpu_insn.c
>> index 97dec18e6989..a8b93aa4d8ec 100644
>> --- a/arch/riscv/kvm/vcpu_insn.c
>> +++ b/arch/riscv/kvm/vcpu_insn.c
>> @@ -448,7 +448,12 @@ int kvm_riscv_vcpu_virtual_insn(struct kvm_vcpu *vcpu, struct kvm_run *run,
>> insn = kvm_riscv_vcpu_unpriv_read(vcpu, true,
>> ct->sepc,
>> &utrap);
>> - if (utrap.scause) {
>> + switch (utrap.scause) {
>> + case 0:
>> + break;
>
>This looks like an unrelated change so drop it or send a separate patch
>with proper explanation.
>
>> + case EXC_LOAD_GUEST_PAGE_FAULT:
>> + return KVM_INSN_CONTINUE_SAME_SEPC;
>
>The KVM_INSN_xyz enum values are only for functions called via
>system_opcode_insn() so return 1 over here just like the below
>default case.
>
>Also, add some comments over here about why we are simply
>continuing the guest.
>
>> + default:
>> utrap.sepc = ct->sepc;
>> kvm_riscv_vcpu_trap_redirect(vcpu, &utrap);
>> return 1;
>> @@ -503,7 +508,12 @@ int kvm_riscv_vcpu_mmio_load(struct kvm_vcpu *vcpu, struct kvm_run *run,
>> */
>> insn = kvm_riscv_vcpu_unpriv_read(vcpu, true, ct->sepc,
>> &utrap);
>> - if (utrap.scause) {
>> + switch (utrap.scause) {
>> + case 0:
>> + break;
>
>This looks like an unrelated change so drop it or send a separate patch
>with proper explanation.
>
>> + case EXC_LOAD_GUEST_PAGE_FAULT:
>> + return KVM_INSN_CONTINUE_SAME_SEPC;
>
>Same comment as kvm_riscv_vcpu_virtual_insn().
>
>> + default:
>> /* Redirect trap if we failed to read instruction */
>> utrap.sepc = ct->sepc;
>> kvm_riscv_vcpu_trap_redirect(vcpu, &utrap);
>> @@ -629,7 +639,12 @@ int kvm_riscv_vcpu_mmio_store(struct kvm_vcpu *vcpu, struct kvm_run *run,
>> */
>> insn = kvm_riscv_vcpu_unpriv_read(vcpu, true, ct->sepc,
>> &utrap);
>> - if (utrap.scause) {
>> + switch (utrap.scause) {
>> + case 0:
>> + break;
>
>This looks like an unrelated change so drop it or send a separate patch
>with proper explanation.
>
>> + case EXC_LOAD_GUEST_PAGE_FAULT:
>> + return KVM_INSN_CONTINUE_SAME_SEPC;
>
>Same comment as kvm_riscv_vcpu_virtual_insn().
>
>> + default:
>> /* Redirect trap if we failed to read instruction */
>> utrap.sepc = ct->sepc;
>> kvm_riscv_vcpu_trap_redirect(vcpu, &utrap);
>> --
>> 2.49.0
>>
>>
>
>Regards,
>Anup
Hi Anup:
Thanks for the review.
I will follow your suggestions in the next version.
Thanks,
Fangyu
prev parent reply other threads:[~2025-11-06 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 13:43 fangyu.yu
2025-09-12 14:01 ` fangyu.yu
2025-09-13 1:24 ` fangyu.yu
2025-11-06 6:18 ` Anup Patel
2025-11-06 13:29 ` fangyu.yu [this message]
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=20251106132950.80534-1-fangyu.yu@linux.alibaba.com \
--to=fangyu.yu@linux.alibaba.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=graf@amazon.com \
--cc=guoren@kernel.org \
--cc=jiangyifei@huawei.com \
--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=pbonzini@redhat.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®