From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Xu Lu" <luxu.kernel@bytedance.com>
Cc: <anup@brainfault.org>, <atish.patra@linux.dev>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <alex@ghiti.fr>, <kvm@vger.kernel.org>,
<kvm-riscv@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"linux-riscv" <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [External] Re: [PATCH] RISC-V: KVM: Delegate illegal instruction fault
Date: Mon, 23 Jun 2025 12:04:30 +0200 [thread overview]
Message-ID: <DATTT5U64J4L.3UTDRVT2YP7GT@ventanamicro.com> (raw)
In-Reply-To: <CAPYmKFvcnDJWXAUEX8oY6seQrgwKiZjDqrJ_R2rJ4kWq7RQUSg@mail.gmail.com>
2025-06-22T18:11:49+08:00, Xu Lu <luxu.kernel@bytedance.com>:
> Hi Radim,
>
> On Fri, Jun 20, 2025 at 8:04 PM Radim Krčmář <rkrcmar@ventanamicro.com> wrote:
>>
>> 2025-06-20T17:17:20+08:00, Xu Lu <luxu.kernel@bytedance.com>:
>> > Delegate illegal instruction fault to VS mode in default to avoid such
>> > exceptions being trapped to HS and redirected back to VS.
>> >
>> > Signed-off-by: Xu Lu <luxu.kernel@bytedance.com>
>> > ---
>> > diff --git a/arch/riscv/include/asm/kvm_host.h b/arch/riscv/include/asm/kvm_host.h
>> > @@ -48,6 +48,7 @@
>> > + BIT(EXC_INST_ILLEGAL) | \
>>
>> You should also remove the dead code in kvm_riscv_vcpu_exit.
>
> I only want to delegate it by default. And KVM may still want to
> delegate different exceptions for different VMs like what it does for
> EXC_BREAKPOINT.
(I think we could easily reintroduce the code if KVM wants to do that in
the future. I also think that it's bad that this patch is doing an
observable change without userspace involvement -- the counting of KVM
SBI PMU events, but others will probably disagree with me on this.)
> So maybe it is better to reserve these codes?
Possibly, the current is acceptable if you have considered the
implications on PMU events.
>> And why not delegate the others as well?
>> (EXC_LOAD_MISALIGNED, EXC_STORE_MISALIGNED, EXC_LOAD_ACCESS,
>> EXC_STORE_ACCESS, and EXC_INST_ACCESS.)
>
> Thanks for the reminder. I will have a test and resend the patch if it works.
The misaligned exceptions are already being worked on, so don't waste
your time on them, sorry.
--
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv
WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Xu Lu" <luxu.kernel@bytedance.com>
Cc: <anup@brainfault.org>, <atish.patra@linux.dev>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <alex@ghiti.fr>, <kvm@vger.kernel.org>,
<kvm-riscv@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"linux-riscv" <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [External] Re: [PATCH] RISC-V: KVM: Delegate illegal instruction fault
Date: Mon, 23 Jun 2025 12:04:30 +0200 [thread overview]
Message-ID: <DATTT5U64J4L.3UTDRVT2YP7GT@ventanamicro.com> (raw)
In-Reply-To: <CAPYmKFvcnDJWXAUEX8oY6seQrgwKiZjDqrJ_R2rJ4kWq7RQUSg@mail.gmail.com>
2025-06-22T18:11:49+08:00, Xu Lu <luxu.kernel@bytedance.com>:
> Hi Radim,
>
> On Fri, Jun 20, 2025 at 8:04 PM Radim Krčmář <rkrcmar@ventanamicro.com> wrote:
>>
>> 2025-06-20T17:17:20+08:00, Xu Lu <luxu.kernel@bytedance.com>:
>> > Delegate illegal instruction fault to VS mode in default to avoid such
>> > exceptions being trapped to HS and redirected back to VS.
>> >
>> > Signed-off-by: Xu Lu <luxu.kernel@bytedance.com>
>> > ---
>> > diff --git a/arch/riscv/include/asm/kvm_host.h b/arch/riscv/include/asm/kvm_host.h
>> > @@ -48,6 +48,7 @@
>> > + BIT(EXC_INST_ILLEGAL) | \
>>
>> You should also remove the dead code in kvm_riscv_vcpu_exit.
>
> I only want to delegate it by default. And KVM may still want to
> delegate different exceptions for different VMs like what it does for
> EXC_BREAKPOINT.
(I think we could easily reintroduce the code if KVM wants to do that in
the future. I also think that it's bad that this patch is doing an
observable change without userspace involvement -- the counting of KVM
SBI PMU events, but others will probably disagree with me on this.)
> So maybe it is better to reserve these codes?
Possibly, the current is acceptable if you have considered the
implications on PMU events.
>> And why not delegate the others as well?
>> (EXC_LOAD_MISALIGNED, EXC_STORE_MISALIGNED, EXC_LOAD_ACCESS,
>> EXC_STORE_ACCESS, and EXC_INST_ACCESS.)
>
> Thanks for the reminder. I will have a test and resend the patch if it works.
The misaligned exceptions are already being worked on, so don't waste
your time on them, sorry.
WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Xu Lu" <luxu.kernel@bytedance.com>
Cc: <anup@brainfault.org>, <atish.patra@linux.dev>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <alex@ghiti.fr>, <kvm@vger.kernel.org>,
<kvm-riscv@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"linux-riscv" <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [External] Re: [PATCH] RISC-V: KVM: Delegate illegal instruction fault
Date: Mon, 23 Jun 2025 12:04:30 +0200 [thread overview]
Message-ID: <DATTT5U64J4L.3UTDRVT2YP7GT@ventanamicro.com> (raw)
In-Reply-To: <CAPYmKFvcnDJWXAUEX8oY6seQrgwKiZjDqrJ_R2rJ4kWq7RQUSg@mail.gmail.com>
2025-06-22T18:11:49+08:00, Xu Lu <luxu.kernel@bytedance.com>:
> Hi Radim,
>
> On Fri, Jun 20, 2025 at 8:04 PM Radim Krčmář <rkrcmar@ventanamicro.com> wrote:
>>
>> 2025-06-20T17:17:20+08:00, Xu Lu <luxu.kernel@bytedance.com>:
>> > Delegate illegal instruction fault to VS mode in default to avoid such
>> > exceptions being trapped to HS and redirected back to VS.
>> >
>> > Signed-off-by: Xu Lu <luxu.kernel@bytedance.com>
>> > ---
>> > diff --git a/arch/riscv/include/asm/kvm_host.h b/arch/riscv/include/asm/kvm_host.h
>> > @@ -48,6 +48,7 @@
>> > + BIT(EXC_INST_ILLEGAL) | \
>>
>> You should also remove the dead code in kvm_riscv_vcpu_exit.
>
> I only want to delegate it by default. And KVM may still want to
> delegate different exceptions for different VMs like what it does for
> EXC_BREAKPOINT.
(I think we could easily reintroduce the code if KVM wants to do that in
the future. I also think that it's bad that this patch is doing an
observable change without userspace involvement -- the counting of KVM
SBI PMU events, but others will probably disagree with me on this.)
> So maybe it is better to reserve these codes?
Possibly, the current is acceptable if you have considered the
implications on PMU events.
>> And why not delegate the others as well?
>> (EXC_LOAD_MISALIGNED, EXC_STORE_MISALIGNED, EXC_LOAD_ACCESS,
>> EXC_STORE_ACCESS, and EXC_INST_ACCESS.)
>
> Thanks for the reminder. I will have a test and resend the patch if it works.
The misaligned exceptions are already being worked on, so don't waste
your time on them, sorry.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-06-23 10:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 9:17 [PATCH] RISC-V: KVM: Delegate illegal instruction fault Xu Lu
2025-06-20 9:17 ` Xu Lu
2025-06-20 9:17 ` Xu Lu
2025-06-20 12:04 ` Radim Krčmář
2025-06-20 12:04 ` Radim Krčmář
2025-06-20 12:04 ` Radim Krčmář
2025-06-22 10:11 ` [External] " Xu Lu
2025-06-22 10:11 ` Xu Lu
2025-06-22 10:11 ` Xu Lu
2025-06-23 10:04 ` Radim Krčmář [this message]
2025-06-23 10:04 ` Radim Krčmář
2025-06-23 10:04 ` Radim Krčmář
2025-06-23 10:29 ` Xu Lu
2025-06-23 10:29 ` Xu Lu
2025-06-23 10:29 ` Xu Lu
2025-06-23 8:04 ` Clément Léger
2025-06-23 8:04 ` Clément Léger
2025-06-23 8:04 ` Clément Léger
2025-06-23 9:54 ` Radim Krčmář
2025-06-23 9:54 ` Radim Krčmář
2025-06-23 9:54 ` Radim Krčmář
2025-06-23 12:12 ` [External] " Xu Lu
2025-06-23 12:12 ` Xu Lu
2025-06-23 12:12 ` Xu Lu
2025-06-23 12:35 ` Clément Léger
2025-06-23 12:35 ` Clément Léger
2025-06-23 12:35 ` Clément Léger
2025-06-23 13:30 ` Xu Lu
2025-06-23 13:30 ` Xu Lu
2025-06-23 13:30 ` Xu Lu
2025-06-23 13:42 ` Clément Léger
2025-06-23 13:42 ` Clément Léger
2025-06-23 13:42 ` Clément Léger
2025-06-23 14:09 ` Xu Lu
2025-06-23 14:09 ` Xu Lu
2025-06-23 14:09 ` Xu Lu
2025-06-23 14:11 ` Clément Léger
2025-06-23 14:11 ` Clément Léger
2025-06-23 14:11 ` 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=DATTT5U64J4L.3UTDRVT2YP7GT@ventanamicro.com \
--to=rkrcmar@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv-bounces@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.