From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Suzuki K Poulose <Suzuki.Poulose@arm.com>
Subject: Re: [PATCH v2 0/2] arm64: Taint the kernel on different GMID_EL1.BS
Date: Wed, 26 May 2021 23:15:41 +0100 [thread overview]
Message-ID: <162206310822.1583551.15098387661077746083.b4-ty@kernel.org> (raw)
In-Reply-To: <20210526193621.21559-1-catalin.marinas@arm.com>
On Wed, 26 May 2021 20:36:19 +0100, Catalin Marinas wrote:
> An updated version of the GMID_EL1.BS sanity check since the first one
> broke the boot on CPUs not supporting MTE.
>
> Changes since v1 [1]:
>
> - Add an id_aa64pfr1_mte() function to check whether the CPU supports
> MTE before reading the GMID_EL1 register and updating the sanitised
> one
>
> [...]
Applied to arm64 (for-next/cpufeature), thanks!
[1/2] arm64: Change the cpuinfo_arm64 member type for some sysregs to u64
https://git.kernel.org/arm64/c/7513cc8a1b74
[2/2] arm64: Check if GMID_EL1.BS is the same on all CPUs
https://git.kernel.org/arm64/c/21047e91a5a6
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-05-26 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 19:36 [PATCH v2 0/2] arm64: Taint the kernel on different GMID_EL1.BS Catalin Marinas
2021-05-26 19:36 ` [PATCH v2 1/2] arm64: Change the cpuinfo_arm64 member type for some sysregs to u64 Catalin Marinas
2021-05-26 19:36 ` [PATCH v2 2/2] arm64: Check if GMID_EL1.BS is the same on all CPUs Catalin Marinas
2021-05-26 22:15 ` 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:
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=162206310822.1583551.15098387661077746083.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Suzuki.Poulose@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.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).