From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, will@kernel.org, maz@kernel.org
Subject: Re: [PATCH kvmtool] aarch64: Give up with MTE for AArch32 guest
Date: Fri, 20 May 2022 14:31:03 +0100 [thread overview]
Message-ID: <YoeYF/J2O/cLXmXZ@monolith.localdoman> (raw)
In-Reply-To: <20220520123844.127733-1-vladimir.murzin@arm.com>
Hi Vladimir,
When I run an --aarch32 guest with --debug this is the message that I'm
getting:
Info: (arm/aarch64/kvm.c) kvm__arch_enable_mte:146: MTE capability not available
Would you mind elaborating on the merits of the message that you are
proposing:
Info: (arm/aarch64/kvm.c) kvm__arch_enable_mte:124: MTE is incompatible with AArch32
Is it because it explains why the capability is not available?
Thanks,
Alex
On Fri, May 20, 2022 at 01:38:44PM +0100, Vladimir Murzin wrote:
> KVM doesn't support combination of MTE and AArch32 guest, so do not
> even try.
>
> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> ---
> arm/aarch64/kvm.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arm/aarch64/kvm.c b/arm/aarch64/kvm.c
> index 1b992dd..f3fe854 100644
> --- a/arm/aarch64/kvm.c
> +++ b/arm/aarch64/kvm.c
> @@ -120,6 +120,11 @@ void kvm__arch_enable_mte(struct kvm *kvm)
> .cap = KVM_CAP_ARM_MTE,
> };
>
> + if (kvm->cfg.arch.aarch32_guest) {
> + pr_debug("MTE is incompatible with AArch32");
> + return;
> + }
> +
> if (kvm->cfg.arch.mte_disabled) {
> pr_debug("MTE disabled by user");
> return;
> --
> 2.25.1
>
_______________________________________________
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:[~2022-05-20 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 12:38 [PATCH kvmtool] aarch64: Give up with MTE for AArch32 guest Vladimir Murzin
2022-05-20 13:31 ` Alexandru Elisei [this message]
2022-05-20 13:48 ` Vladimir Murzin
2022-05-20 14:01 ` Alexandru Elisei
2022-05-20 20:51 ` Will Deacon
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=YoeYF/J2O/cLXmXZ@monolith.localdoman \
--to=alexandru.elisei@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=vladimir.murzin@arm.com \
--cc=will@kernel.org \
/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