From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
kernel-team@android.com, ardb@kernel.org
Subject: Re: [PATCH 0/2] arm64: cpucap handling cleanups
Date: Wed, 13 Dec 2023 17:39:24 +0000 [thread overview]
Message-ID: <ZXnsTHbRxe7b7YNL@FVFF77S0Q05N> (raw)
In-Reply-To: <170248332281.2991306.7731192579703060918.b4-ty@kernel.org>
On Wed, Dec 13, 2023 at 05:25:18PM +0000, Will Deacon wrote:
> On Tue, 12 Dec 2023 17:09:08 +0000, Mark Rutland wrote:
> > The recent changes to remove cpus_have_const_cap() left a period between
> > detecting cpucaps and patching alternatives where it is necessary to use
> > cpus_have_cap() to check that a cpucap has been detected. During this
> > period we do a few things, and there's a risk that code using a mixture
> > of cpus_have_cap() and alternative_has_cap_*() sees an inconsistent
> > state.
> >
> > [...]
>
> Applied to arm64 (for-next/cpufeature), thanks!
>
> Basing the series on for-next/fixes makes it fiddly to manage, so I
> dropped the kpti_install_ng_mappings() hunk from patch 1 and will
> re-introduce it when I merge the branches together.
Thanks, and sorry for the hassle!
The changes and resolution in that branch look good to me (and build and boot
cleanly); I'll go throw that on my test system and see if anything blows up
overnight.
Mark.
> [1/2] arm64: Cleanup system cpucap handling
> https://git.kernel.org/arm64/c/63a2d92e1461
> [2/2] arm64: Align boot cpucap handling with system cpucap handling
> https://git.kernel.org/arm64/c/eb15d707c252
>
> 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:[~2023-12-13 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 17:09 [PATCH 0/2] arm64: cpucap handling cleanups Mark Rutland
2023-12-12 17:09 ` [PATCH 1/2] arm64: Cleanup system cpucap handling Mark Rutland
2023-12-12 17:09 ` [PATCH 2/2] arm64: Align boot cpucap handling with " Mark Rutland
2023-12-13 17:25 ` [PATCH 0/2] arm64: cpucap handling cleanups Will Deacon
2023-12-13 17:39 ` Mark Rutland [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=ZXnsTHbRxe7b7YNL@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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