From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Andrew Jones" <ajones@ventanamicro.com>,
"Meng Zhuo" <mengzhuo@iscas.ac.cn>
Cc: <qemu-devel@nongnu.org>, <qemu-riscv@nongnu.org>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
<qemu-riscv-bounces+qemu-riscv=archiver.kernel.org@nongnu.org>
Subject: Re: [PATCH] target/riscv: add satp mode for kvm host cpu
Date: Mon, 28 Apr 2025 11:30:36 +0200 [thread overview]
Message-ID: <D9I60P8TG036.2ZHSS9EHW4W8N@ventanamicro.com> (raw)
In-Reply-To: <20250428-00fc862d2d2d628ffa4c8547@orel>
2025-04-28T09:00:55+02:00, Andrew Jones <ajones@ventanamicro.com>:
> On Sun, Apr 27, 2025 at 09:25:57PM +0800, Meng Zhuo wrote:
>> This patch adds host satp mode while kvm/host cpu satp mode is not
>> set.
>
> Huh, the KVM side[1] was written for this purpose, but it appears we never
> got a QEMU side merged.
>
> [1] commit 2776421e6839 ("RISC-V: KVM: provide UAPI for host SATP mode")
KVM satp_mode is the current SATP.mode and I don't think the other
SATP.modes can generally be guessed from the host SATP mode.
Can't QEMU use the host capabilities from cpuinfo or something?
Do we need to return a bitmask from KVM?
(e.g. WARL all modes in vsatp and return what sticks.)
Thanks.
next prev parent reply other threads:[~2025-04-28 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 13:25 [PATCH] target/riscv: add satp mode for kvm host cpu Meng Zhuo
2025-04-28 7:00 ` Andrew Jones
2025-04-28 9:30 ` Radim Krčmář [this message]
2025-04-28 12:08 ` Andrew Jones
2025-04-28 13:37 ` Radim Krčmář
2025-04-28 15:36 ` Andrew Jones
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=D9I60P8TG036.2ZHSS9EHW4W8N@ventanamicro.com \
--to=rkrcmar@ventanamicro.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=mengzhuo@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv-bounces+qemu-riscv=archiver.kernel.org@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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.