Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: kvmarm@lists.linux.dev, nikos.nikoleris@arm.com,
	andrew.jones@linux.dev, eric.auger@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2] arm64: Add basic MTE test
Date: Thu, 2 Jan 2025 13:23:24 +0000	[thread overview]
Message-ID: <Z3aTTJWSKL3OK9dY@raptor> (raw)
In-Reply-To: <6db97d9c-abe0-4418-903f-bc4662a8cab0@arm.com>

Hi Vladimir,

On Thu, Jan 02, 2025 at 12:10:05PM +0000, Vladimir Murzin wrote:
> Hi Alexandru,
> 
> On 1/2/25 11:45, Alexandru Elisei wrote:
> > Hi Vladimir,
> > 
> > On Thu, Jan 02, 2025 at 10:04:37AM +0000, Vladimir Murzin wrote:
> > [..]
> >> On 12/30/24 15:19, Alexandru Elisei wrote:
> >>> Hi Vladimir,
> >>> 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?
> >>>
> >> ./configure --arch=arm64 --processor=max
> > Ah, so that explains it. Would you mind adding this information to the commit
> > message, perhaps something like this:
> > 
> > If using TCG as the accelerator, qemu must emulate a CPU that supports MTE
> > in order for the tests to run. Use configure --processor to set an
> > appropriate CPU. If unsure about a particular processor, 'max' will most
> > likely work with a new enough qemu version.
> > 
> 
> Yes, I can add it when re-spin v4 (sorry just sent v3). Alternatively, we can
> merge change defaulting processor to `max` for arm64 which IMO much better
> solution (and does not require me to re-spin the patch) ;-)

I'm going to send patches to make 'max' the default, so no need to respin :)

Thanks,
Alex

> 
> Cheers
> Vladimir
> 
> >> Thanks
> >> Vladimir
> >>
> >>> Thanks,
> >>> Alex
> >>>
> 

  reply	other threads:[~2025-01-02 13:23 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
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 [this message]
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=Z3aTTJWSKL3OK9dY@raptor \
    --to=alexandru.elisei@arm.com \
    --cc=andrew.jones@linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox