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: Andrew Jones <drjones@redhat.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] arm: enable MTE for QEMU + kvm
Date: Thu, 30 Jun 2022 18:09:22 +0200 [thread overview]
Message-ID: <87lete2kwd.fsf@redhat.com> (raw)
In-Reply-To: <b684d1e6-2d8f-5d08-aae0-b085a722575b@redhat.com>
On Wed, Jun 29 2022, Eric Auger <eauger@redhat.com> wrote:
> Hi Connie,
>
> On 6/13/22 18:02, Cornelia Huck wrote:
>> On Fri, Jun 10 2022, Eric Auger <eauger@redhat.com> wrote:
>>
>>> Hi Connie,
>>>
>>> On 5/12/22 15:11, Cornelia Huck wrote:
>>>> This series enables MTE for kvm guests, if the kernel supports it.
>>>> Lightly tested while running under the simulator (the arm64/mte/
>>>> kselftests pass... if you wait patiently :)
>>>>
>>>> A new cpu property "mte" (defaulting to on if possible) is introduced;
>>>> for tcg, you still need to enable mte at the machine as well.
>>> isn't the property set to off by default when kvm is enabled (because of
>>> the migration blocker).
>>
>> Oh, I had changed that around several times, and it seems I ended up
>> being confused when I wrote this cover letter... I wonder what the best
>> state would be (assuming that I don't manage to implement it soonish,
>> but it seems we still would need kernel changes as by the discussion in
>> that other patch series.)
> Having mte=off by default along with KVM, until the migration gets
> supported, looks OK to me. Does it prevent you from having it set to
> another value by default with TCG (depending on the virt machine
> tag_memory option)?
>
> tag_memory=on tag_memory=off
> KVM CPU mte=off invalid mte=off
> KVM CPU mte=on invalid mte=on
> TCG CPU mte=off invalid mte=off
> TCG CPU mte=on mte=on invalid
>
> default value:
> KVM mte = off until migration gets supported
> TCG mte = machine.tag_memory
With OnOffAuto, I currently have:
valid for tcg: cpu.mte=on, tag_memory=on (result: mte on)
cpu.mte=off, tag_memory either on or off (result: mte off)
cpu.mte unspecified, tag_memory either on or off (result:
mte==tag_memory)
valid for kvm: tag_memory always off
cpu.mte=off (result: mte off)
cpu.mte=on if mte supported in kvm (result: mte on)
cpu.mte unspecified (result: mte on if kvm supports it;
this I can flip)
all other combinations: error
prev parent reply other threads:[~2022-06-30 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 13:11 [PATCH RFC 0/2] arm: enable MTE for QEMU + kvm Cornelia Huck
2022-05-12 13:11 ` [PATCH RFC 1/2] arm/kvm: enable MTE if available Cornelia Huck
2022-06-10 20:48 ` Eric Auger
2022-06-14 8:40 ` Cornelia Huck
2022-06-29 10:38 ` Eric Auger
2022-06-30 15:55 ` Cornelia Huck
2022-05-12 13:11 ` [PATCH RFC 2/2] qtests/arm: add some mte tests Cornelia Huck
2022-05-31 9:29 ` [PATCH RFC 0/2] arm: enable MTE for QEMU + kvm Cornelia Huck
2022-06-08 10:14 ` Cornelia Huck
2022-06-10 20:40 ` Eric Auger
2022-06-13 16:02 ` Cornelia Huck
2022-06-29 10:27 ` Eric Auger
2022-06-30 16:09 ` Cornelia Huck [this message]
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=87lete2kwd.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=drjones@redhat.com \
--cc=eauger@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=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).