From: Mark Rutland <mark.rutland@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>,
ardb@kernel.org, joey.gouly@arm.com, maz@kernel.org,
james.morse@arm.com
Subject: Re: [PATCH v2 0/8] arm64: alternatives: improvements
Date: Sat, 17 Sep 2022 13:46:35 +0100 [thread overview]
Message-ID: <YyXBq9jR6jFeX+vJ@FVFF77S0Q05N> (raw)
In-Reply-To: <166335025268.1744272.4179216542809756286.b4-ty@arm.com>
On Fri, Sep 16, 2022 at 06:46:20PM +0100, Catalin Marinas wrote:
> On Mon, 12 Sep 2022 17:22:02 +0100, Mark Rutland wrote:
> > This series reworks the arm64 alternatives code. The major aim is to
> > make the patching code more consistent and robust, and as a benefit we
> > can also make the kernel Image smaller.
> >
> > Largely, the series makes two structural changes:
> >
> > 1) Replacing cpucap static branches with equivalent alternatives.
> >
> > [...]
>
> Applied to arm64 (for-next/alternatives), thanks!
>
> There's a slight conflict in the apply_alternatives_vdso() function
> introduced by Joey but I fixed it up locally. The ARM64_NPATCHABLE
> disappeared with Mark's reworking.
Sorry about that, and thanks for the fixup!
IIUC that just needed a s/ARM64_NPATCHABLE/ARM64_NCAPS/, and the resulting code
in commit ebbb0b0b37249038 looks right to me.
Thanks,
Mark.
> [1/8] arm64: cpufeature: make cpus_have_cap() noinstr-safe
> https://git.kernel.org/arm64/c/92b4b5619f12
> [2/8] arm64: alternatives: kvm: prepare for cap changes
> https://git.kernel.org/arm64/c/34bbfdfb146b
> [3/8] arm64: alternatives: proton-pack: prepare for cap changes
> https://git.kernel.org/arm64/c/747ad8d55764
> [4/8] arm64: alternatives: hoist print out of __apply_alternatives()
> https://git.kernel.org/arm64/c/c5ba03260c7a
> [5/8] arm64: alternatives: make alt_region const
> https://git.kernel.org/arm64/c/b723edf3a12a
> [6/8] arm64: alternatives: have callbacks take a cap
> https://git.kernel.org/arm64/c/4c0bd995d73e
> [7/8] arm64: alternatives: add alternative_has_feature_*()
> https://git.kernel.org/arm64/c/21fb26bfb01f
> [8/8] arm64: alternatives: add shared NOP callback
> https://git.kernel.org/arm64/c/d926079f17bf
>
> --
> Catalin
>
_______________________________________________
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:[~2022-09-17 12:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 16:22 [PATCH v2 0/8] arm64: alternatives: improvements Mark Rutland
2022-09-12 16:22 ` [PATCH v2 1/8] arm64: cpufeature: make cpus_have_cap() noinstr-safe Mark Rutland
2022-09-12 16:22 ` [PATCH v2 2/8] arm64: alternatives: kvm: prepare for cap changes Mark Rutland
2022-09-12 16:22 ` [PATCH v2 3/8] arm64: alternatives: proton-pack: " Mark Rutland
2022-09-12 16:22 ` [PATCH v2 4/8] arm64: alternatives: hoist print out of __apply_alternatives() Mark Rutland
2022-09-12 16:22 ` [PATCH v2 5/8] arm64: alternatives: make alt_region const Mark Rutland
2022-09-12 16:22 ` [PATCH v2 6/8] arm64: alternatives: have callbacks take a cap Mark Rutland
2022-09-27 9:31 ` Jon Hunter
2022-09-29 9:53 ` Jon Hunter
2022-09-29 10:10 ` Ard Biesheuvel
2022-09-29 10:48 ` Jon Hunter
2022-09-29 10:47 ` Mark Rutland
2022-09-29 11:01 ` Jon Hunter
2022-09-29 11:09 ` Mark Rutland
2022-09-29 13:37 ` Jon Hunter
2022-09-29 14:38 ` Mark Rutland
2022-09-12 16:22 ` [PATCH v2 7/8] arm64: alternatives: add alternative_has_feature_*() Mark Rutland
2022-09-16 11:13 ` Catalin Marinas
2022-09-17 12:52 ` Mark Rutland
2022-09-19 17:01 ` Nathan Chancellor
2022-09-20 12:09 ` Mark Rutland
2022-09-20 13:31 ` Nathan Chancellor
2022-09-12 16:22 ` [PATCH v2 8/8] arm64: alternatives: add shared NOP callback Mark Rutland
2022-09-13 13:36 ` [PATCH v2 0/8] arm64: alternatives: improvements Ard Biesheuvel
2022-09-16 17:46 ` Catalin Marinas
2022-09-17 12:46 ` 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=YyXBq9jR6jFeX+vJ@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.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