archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <>
To: Catalin Marinas <>,
	Mark Brown <>
Cc:, Will Deacon <>,,
	Marc Zyngier <>
Subject: Re: [PATCH] arm64: Document requirement for access to FEAT_HCX
Date: Tue, 25 May 2021 19:58:44 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 12 May 2021 17:23:50 +0100, Mark Brown wrote:
> v8.7 of the architecture introduced FEAT_HCX which adds an additional
> hypervisor configuration register HCRX_EL2. Even though Linux does not
> currently make use of this feature let's document that the EL3 trap for
> access to the register should be disabled so that we are able to make
> use of it in future.

Applied to arm64 (for-next/docs), thanks!

[1/1] arm64: Document requirement for access to FEAT_HCX


linux-arm-kernel mailing list

      parent reply	other threads:[~2021-05-25 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 16:23 [PATCH] arm64: Document requirement for access to FEAT_HCX Mark Brown
2021-05-14 11:01 ` Catalin Marinas
2021-05-25 18:58 ` Will Deacon [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).