From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Clément Léger" <cleger@rivosinc.com>,
"Xu Lu" <luxu.kernel@bytedance.com>,
anup@brainfault.org, atish.patra@linux.dev,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr
Cc: <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: [PATCH] RISC-V: KVM: Delegate illegal instruction fault
Date: Mon, 23 Jun 2025 11:54:56 +0200 [thread overview]
Message-ID: <DATTLU8NTTUV.1L05K3TTMV29X@ventanamicro.com> (raw)
In-Reply-To: <1d9ad2a8-6ab5-4f5e-b514-4a902392e074@rivosinc.com>
2025-06-23T10:04:45+02:00, Clément Léger <cleger@rivosinc.com>:
> On 20/06/2025 14:04, Radim Krčmář wrote:
>> And why not delegate the others as well?
>> (EXC_LOAD_MISALIGNED, EXC_STORE_MISALIGNED, EXC_LOAD_ACCESS,
>> EXC_STORE_ACCESS, and EXC_INST_ACCESS.)
>
> Currently, OpenSBI does not delegate misaligned exception by default and
> handles misaligned access by itself, this is (partially) why we added
> the FWFT SBI extension to request such delegation. Since some supervisor
> software expect that default, they do not have code to handle misaligned
> accesses emulation. So they should not be delegated by default.
Yeah, I forgot about your patches that conflict with the change, thanks.
(The current KVM exception handler only forwards all the listed
exceptions, so the only observable difference this change would make is
that the KVM SBI PMU event is not counted.)
_______________________________________________
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:25 UTC|newest]
Thread overview: 13+ 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 12:04 ` Radim Krčmář
2025-06-22 10:11 ` [External] " Xu Lu
2025-06-23 10:04 ` Radim Krčmář
2025-06-23 10:29 ` Xu Lu
2025-06-23 8:04 ` Clément Léger
2025-06-23 9:54 ` Radim Krčmář [this message]
2025-06-23 12:12 ` [External] " Xu Lu
2025-06-23 12:35 ` Clément Léger
2025-06-23 13:30 ` Xu Lu
2025-06-23 13:42 ` Clément Léger
2025-06-23 14:09 ` Xu Lu
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=DATTLU8NTTUV.1L05K3TTMV29X@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=cleger@rivosinc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox