From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>
Cc: James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
steven.price@arm.com, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: arm64: Handle MTE Set/Way CMOs
Date: Tue, 23 May 2023 16:13:15 +0000 [thread overview]
Message-ID: <ZGzmGxkL7x7+rokE@linux.dev> (raw)
In-Reply-To: <20230515204601.1270428-1-maz@kernel.org>
On Mon, May 15, 2023 at 09:45:59PM +0100, Marc Zyngier wrote:
> When the MTE support was added, it seens the handling of MTE Set/Way
> was ommited, meaning that the guest will get an UNDEF if it tries to
> do something that is quite stupid, but still allowed by the
> architecture...
>
> Found by inspection while writting the trap support for NV.
>
> Marc Zyngier (2):
> arm64: Add missing Set/Way CMO encodings
> KVM: arm64: Handle trap of tagged Set/Way CMOs
For the series:
Reviewed-by: Oliver Upton <oliver.upton@linux.dev>
--
Thanks,
Oliver
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-23 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 20:45 [PATCH 0/2] KVM: arm64: Handle MTE Set/Way CMOs Marc Zyngier
2023-05-15 20:46 ` [PATCH 1/2] arm64: Add missing Set/Way CMO encodings Marc Zyngier
2023-05-17 10:23 ` Cornelia Huck
2023-05-15 20:46 ` [PATCH 2/2] KVM: arm64: Handle trap of tagged Set/Way CMOs Marc Zyngier
2023-05-17 10:24 ` Cornelia Huck
2023-05-17 10:06 ` [PATCH 0/2] KVM: arm64: Handle MTE " Steven Price
2023-05-23 16:13 ` Oliver Upton [this message]
2023-05-24 12:49 ` Marc Zyngier
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=ZGzmGxkL7x7+rokE@linux.dev \
--to=oliver.upton@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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).