From: Marc Zyngier <maz@kernel.org>
To: Kristina Martsenko <kristina.martsenko@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>,
Luis Machado <luis.machado@arm.com>,
Vladimir Murzin <vladimir.murzin@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/11] KVM: arm64: hide MOPS from guests
Date: Sat, 03 Jun 2023 09:42:18 +0100 [thread overview]
Message-ID: <87ttvpndhx.wl-maz@kernel.org> (raw)
In-Reply-To: <20230509142235.3284028-7-kristina.martsenko@arm.com>
On Tue, 09 May 2023 15:22:30 +0100,
Kristina Martsenko <kristina.martsenko@arm.com> wrote:
>
> As FEAT_MOPS is not supported in guests yet, hide it from the ID
> registers for guests.
>
> The MOPS instructions are UNDEFINED in guests as HCRX_EL2.MSCEn is not
> set in HCRX_GUEST_FLAGS, and will take an exception to EL1 if executed.
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Kristina Martsenko <kristina.martsenko@arm.com>
This is very likely to clash with Jing's series that completely
reworks the whole idreg series, but as long as this is on its own
branch, we can deal with that.
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
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-06-03 8:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230509142235.3284028-1-kristina.martsenko@arm.com>
[not found] ` <20230509142235.3284028-2-kristina.martsenko@arm.com>
2023-06-02 13:49 ` [PATCH v2 01/11] KVM: arm64: initialize HCRX_EL2 Catalin Marinas
2023-06-05 15:41 ` Oliver Upton
2023-06-03 8:39 ` Marc Zyngier
[not found] ` <20230509142235.3284028-4-kristina.martsenko@arm.com>
2023-06-02 13:51 ` [PATCH v2 03/11] KVM: arm64: switch HCRX_EL2 between host and guest Catalin Marinas
2023-06-05 15:41 ` Oliver Upton
2023-06-03 8:40 ` Marc Zyngier
[not found] ` <20230509142235.3284028-7-kristina.martsenko@arm.com>
2023-05-25 19:26 ` [PATCH v2 06/11] KVM: arm64: hide MOPS from guests Colton Lewis
2023-05-30 16:34 ` Kristina Martsenko
2023-06-03 8:42 ` Marc Zyngier [this message]
2023-06-05 15:45 ` Oliver Upton
[not found] ` <20230509142235.3284028-8-kristina.martsenko@arm.com>
2023-05-25 19:50 ` [PATCH v2 07/11] arm64: mops: handle MOPS exceptions Colton Lewis
2023-05-30 16:36 ` Kristina Martsenko
2023-06-05 11:43 ` Shaoqin Huang
2023-06-05 12:04 ` Catalin Marinas
2023-06-05 17:46 ` [PATCH v2 00/11] arm64: Support for Armv8.8 memcpy instructions in userspace Catalin Marinas
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=87ttvpndhx.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kristina.martsenko@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.machado@arm.com \
--cc=mark.rutland@arm.com \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=vladimir.murzin@arm.com \
--cc=will@kernel.org \
--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).