From: Richard Henderson <richard.henderson@linaro.org>
To: Cornelia Huck <cohuck@redhat.com>, quintela@redhat.com
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Eric Auger" <eauger@redhat.com>, "Gavin Shan" <gshan@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Andrea Bolognani" <abologna@redhat.com>
Subject: Re: [PATCH v7 1/1] arm/kvm: add support for MTE
Date: Tue, 2 May 2023 11:58:46 +0100 [thread overview]
Message-ID: <2c70f6a6-9e13-3412-8e65-43675fda4d95@linaro.org> (raw)
In-Reply-To: <871qjzcdgi.fsf@redhat.com>
On 5/2/23 10:03, Cornelia Huck wrote:
> Has anyone been able to access a real system with MTE? (All the systems
> where I had hoped that MTE would be available didn't have MTE in the end
> so far, so I'd be interested to hear if anybody else already got to play
> with one.) Honestly, I don't want to even try to test migration if I only
> have access to MTE on the FVP...
Well there's always MTE on QEMU with TCG. :-)
But I agree that while it's better than FVP, it's still slow, and difficult to test
anything at scale. I have no objection to getting non-migratable MTE on KVM in before
attempting to solve migration.
r~
next prev parent reply other threads:[~2023-05-02 10:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 9:55 [PATCH v7 0/1] arm: enable MTE for QEMU + kvm Cornelia Huck
2023-04-28 9:55 ` [PATCH v7 1/1] arm/kvm: add support for MTE Cornelia Huck
2023-04-28 17:50 ` Juan Quintela
2023-05-01 9:37 ` Richard Henderson
2023-05-02 9:03 ` Cornelia Huck
2023-05-02 10:17 ` Juan Quintela
2023-05-02 10:58 ` Richard Henderson [this message]
2023-05-04 15:01 ` Cornelia Huck
2023-05-05 15:14 ` Richard Henderson
2023-05-16 13:48 ` Peter Maydell
2023-05-16 20:31 ` Richard Henderson
2023-05-18 10:09 ` [PATCH v7 0/1] arm: enable MTE for QEMU + kvm Peter Maydell
2023-05-22 12:04 ` Cornelia Huck
2023-05-29 10:15 ` Andrea Bolognani
2023-05-29 10:27 ` Peter Maydell
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=2c70f6a6-9e13-3412-8e65-43675fda4d95@linaro.org \
--to=richard.henderson@linaro.org \
--cc=abologna@redhat.com \
--cc=cohuck@redhat.com \
--cc=eauger@redhat.com \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).