From: Andrew Jones <andrew.jones@linux.dev>
To: Jesse Taube <jesse@rivosinc.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
kvm-riscv@lists.infradead.org, alexandru.elisei@arm.com,
cleger@rivosinc.com, jamestiotio@gmail.com,
Atish Patra <atishp@rivosinc.com>
Subject: Re: [kvm-unit-tests PATCH 2/2] riscv: Add kvmtool support
Date: Mon, 7 Jul 2025 19:44:21 +0200 [thread overview]
Message-ID: <20250707-cdad2acc36fb5c313042bd86@orel> (raw)
In-Reply-To: <CALSpo=YKMa142xhS8KSEenBLemaK6rqYKEd3FotQtCjpV5CciQ@mail.gmail.com>
On Mon, Jul 07, 2025 at 08:28:30AM -0700, Jesse Taube wrote:
> On Fri, Jul 4, 2025 at 8:13 AM Andrew Jones <andrew.jones@linux.dev> wrote:
> >
> > arm/arm64 supports running tests with kvmtool as a first class citizen.
> > Most the code to do that is in the common scripts, so just add the riscv
> > specific bits needed to allow riscv to use kvmtool as a first class
> > citizen too.
> >
> > Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
>
> Reviewed-by: Jesse Taube <jesse@rivosinc.com>
Thanks!
...
> > else
> > - if [ "$arch" != "arm64" ] && [ "$arch" != "arm" ]; then
> > + if [ "$arch" != "arm" ] && [ "$arch" != "arm64" ] &&
> > + [ "$arch" != "riscv32" ] && [ "$arch" != "riscv64" ]; then
>
> Are there plans to add i386 and x86_64 too?
I don't have plans myself, at least not right now, but I think it'd be
good to do it, so it'd be great if somebody would write the patch and
do the testing.
...
> > + command="$(timeout_cmd) $kvmtool run"
> > + if ( [ "$HOST" = "riscv64" ] && [ "$ARCH" = "riscv32" ] ) ||
> > + ( [ "$HOST" = "riscv32" ] && [ "$ARCH" = "riscv64" ] ); then
>
> Shouldn't there be a check like this on arm for when [ "$HOST" =
> "arm" ] && [ "$ARCH" = "aarch64" ]?
arm kvm has been long deprecated and removed from Linux so we should
actually remove any references to HOST==arm throughout the framework
too, since it can't happen (any more).
Thanks,
drew
next prev parent reply other threads:[~2025-07-07 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 15:12 [kvm-unit-tests PATCH 0/2] riscv: Add kvmtool support Andrew Jones
2025-07-04 15:12 ` [kvm-unit-tests PATCH 1/2] arm/arm64: Ensure proper host arch with kvmtool Andrew Jones
2025-07-07 15:10 ` Jesse Taube
2025-07-08 3:41 ` Nutty Liu
2025-07-04 15:12 ` [kvm-unit-tests PATCH 2/2] riscv: Add kvmtool support Andrew Jones
2025-07-07 15:28 ` Jesse Taube
2025-07-07 17:44 ` Andrew Jones [this message]
2025-07-08 3:43 ` Nutty Liu
2025-07-08 9:00 ` [kvm-unit-tests PATCH 0/2] " 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=20250707-cdad2acc36fb5c313042bd86@orel \
--to=andrew.jones@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=atishp@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=jamestiotio@gmail.com \
--cc=jesse@rivosinc.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
/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