From: Andrew Jones <andrew.jones@linux.dev>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: Vladimir Murzin <vladimir.murzin@arm.com>,
kvmarm@lists.linux.dev, nikos.nikoleris@arm.com,
eric.auger@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2] arm64: Add basic MTE test
Date: Mon, 30 Dec 2024 17:52:54 +0100 [thread overview]
Message-ID: <20241230-bccb6213d3a71a09a7d32834@orel> (raw)
In-Reply-To: <Z3LKLvkLjId1SeTI@raptor>
On Mon, Dec 30, 2024 at 04:28:30PM +0000, Alexandru Elisei wrote:
> Hi Drew,
>
> On Mon, Dec 30, 2024 at 04:45:01PM +0100, Andrew Jones wrote:
> > On Mon, Dec 30, 2024 at 03:19:48PM +0000, Alexandru Elisei wrote:
> > ...
> > > Interestingly though, when I try to run a test (either with ./run_tests.sh
> > > mte-sync, or by trying out your example), I get this error:
> > >
> > > qemu-system-aarch64: MTE requested, but not supported by the guest CPU
> > >
> > > My guess is that's caused by kvm-unit-tests defaulting to cortex-a57 as the
> > > model CPU. Changing the cpu to 'max' makes the test run. How are you getting
> > > around this on your end?
> > >
> >
> > We can (and I think should) change to 'max' for the default model.
>
> I think so too, something like this maybe?
>
> diff --git a/configure b/configure
> index 86cf1da36467..4babbd5f5e74 100755
> --- a/configure
> +++ b/configure
> @@ -286,7 +286,7 @@ fi
> [ -z "$processor" ] && processor="$arch"
>
> if [ "$processor" = "arm64" ]; then
> - processor="cortex-a57"
> + processor="max"
> elif [ "$processor" = "arm" ]; then
> processor="cortex-a15"
> fi
>
> Can't do the same for arm, because Makefile.arm passes the processor to
> -mcpu and that causes a build error.
I wonder if we can improve the mcpu thing by just selecting some generic
cpu type at this point? Or just dropping it and counting on the compiler
to use generic cpu type? It'd be nice to use max for both arm and arm64,
but if nobody has time to do the arm work / testing to be sure we can,
then I'm fine with just a patch changing arm64.
Thanks,
drew
next prev parent reply other threads:[~2024-12-30 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 10:34 [kvm-unit-tests PATCH v2] arm64: Add basic MTE test Vladimir Murzin
2024-12-23 12:03 ` Alexandru Elisei
2024-12-23 14:37 ` Vladimir Murzin
2024-12-30 15:19 ` Alexandru Elisei
2024-12-30 15:45 ` Andrew Jones
2024-12-30 16:28 ` Alexandru Elisei
2024-12-30 16:52 ` Andrew Jones [this message]
2025-01-02 12:27 ` Alexandru Elisei
2025-01-02 12:34 ` Andrew Jones
2025-01-02 10:04 ` Vladimir Murzin
2025-01-02 11:45 ` Alexandru Elisei
2025-01-02 12:10 ` Vladimir Murzin
2025-01-02 13:23 ` Alexandru Elisei
2024-12-30 17:01 ` Nikos Nikoleris
2025-01-02 10:49 ` Vladimir Murzin
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=20241230-bccb6213d3a71a09a7d32834@orel \
--to=andrew.jones@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=eric.auger@redhat.com \
--cc=kvmarm@lists.linux.dev \
--cc=nikos.nikoleris@arm.com \
--cc=vladimir.murzin@arm.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.