From: Cornelia Huck <cohuck@redhat.com>
To: Eric Auger <eauger@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Gavin Shan <gshan@redhat.com>
Subject: Re: [PATCH v4 1/2] arm/kvm: add support for MTE
Date: Thu, 26 Jan 2023 13:15:46 +0100 [thread overview]
Message-ID: <874jsdxzil.fsf@redhat.com> (raw)
In-Reply-To: <877cx9y0t6.fsf@redhat.com>
On Thu, Jan 26 2023, Cornelia Huck <cohuck@redhat.com> wrote:
> On Mon, Jan 23 2023, Eric Auger <eauger@redhat.com> wrote:
>
>> Hi Connie,
>> On 1/11/23 17:13, Cornelia Huck wrote:
>>> if (vms->mte && (kvm_enabled() || hvf_enabled())) {
>>> error_report("mach-virt: %s does not support providing "
>>> - "MTE to the guest CPU",
>>> + "emulated MTE to the guest CPU",
>> each time I read this message I feel difficult to understand it. Why not
>> replacing by
>> "mach-virt does not support tag memory with %s acceleration" or
>> something alike?
>
> Hmm... well, it does not support tag memory with kvm/hvf, and the
> consequence of this is that kvm/hvf cannot provide support for emulated
> mte... what about
>
> "mach-virt: tag memory not supported with %s, emulated MTE cannot be
> provided to the guest CPU"
>
> Might be a bit long, though.
"mach-virt: %s does not support providing emulated MTE to the guest CPU
(tag memory not supported)" seems to align better with the other error
messages in that function.
>
>>> kvm_enabled() ? "KVM" : "HVF");
>>> exit(1);
>>> }
next prev parent reply other threads:[~2023-01-26 12:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 16:13 [PATCH v4 0/2] arm: enable MTE for QEMU + kvm Cornelia Huck
2023-01-11 16:13 ` [PATCH v4 1/2] arm/kvm: add support for MTE Cornelia Huck
2023-01-17 16:16 ` Peter Maydell
2023-01-17 16:50 ` Dr. David Alan Gilbert
2023-01-17 16:59 ` Cornelia Huck
2023-01-17 17:11 ` Dr. David Alan Gilbert
2023-01-17 17:01 ` Peter Maydell
2023-01-17 17:53 ` Dr. David Alan Gilbert
2023-01-17 16:52 ` Cornelia Huck
2023-01-17 19:37 ` Richard Henderson
2023-01-18 17:37 ` Cornelia Huck
2023-01-23 13:50 ` Eric Auger
2023-01-26 11:47 ` Cornelia Huck
2023-01-26 12:15 ` Cornelia Huck [this message]
2023-01-11 16:13 ` [PATCH v4 2/2] qtests/arm: add some mte tests Cornelia Huck
2023-01-17 7:21 ` Philippe Mathieu-Daudé
2023-01-23 14:29 ` Eric Auger
2023-01-26 10:57 ` Cornelia Huck
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=874jsdxzil.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eauger@redhat.com \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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).