From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Ard Biesheuvel <ardb@kernel.org>
Cc: mark.rutland@arm.com, anders.roxell@linaro.org, arnd@arndb.de,
Suzuki K Poulose <suzuki.poulose@arm.com>,
catalin.marinas@arm.com, Will Deacon <will@kernel.org>,
James Morse <james.morse@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
kernel-team@android.com, Dave P Martin <dave.martin@arm.com>
Subject: Re: [PATCH] arm64/alternatives: use subsections for replacement sequences
Date: Thu, 2 Jul 2020 14:54:35 +0100 [thread overview]
Message-ID: <159369107379.3020197.4937110667602244064.b4-ty@kernel.org> (raw)
In-Reply-To: <20200630081921.13443-1-ardb@kernel.org>
On Tue, 30 Jun 2020 10:19:21 +0200, Ard Biesheuvel wrote:
> When building very large kernels, the logic that emits replacement
> sequences for alternatives fails when relative branches are present
> in the code that is emitted into the .altinstr_replacement section
> and patched in at the original site and fixed up. The reason is that
> the linker will insert veneers if relative branches go out of range,
> and due to the relative distance of the .altinstr_replacement from
> the .text section where its branch targets usually live, veneers
> may be emitted at the end of the .altinstr_replacement section, with
> the relative branches in the sequence pointed at the veneers instead
> of the actual target.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/alternatives: use subsections for replacement sequences
https://git.kernel.org/arm64/c/f7b93d42945c
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
next prev parent reply other threads:[~2020-07-02 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 8:19 [PATCH] arm64/alternatives: use subsections for replacement sequences Ard Biesheuvel
2020-07-01 17:00 ` Dave P Martin
2020-07-01 17:30 ` Ard Biesheuvel
2020-07-01 17:32 ` Ard Biesheuvel
2020-07-06 15:50 ` Dave Martin
2020-07-06 16:04 ` Ard Biesheuvel
2020-07-07 10:35 ` Dave Martin
2020-07-02 11:56 ` Will Deacon
2020-07-02 13:54 ` Will Deacon [this message]
2020-07-09 10:57 ` Alexandru Elisei
2020-07-09 11:12 ` Alexandru Elisei
2020-07-09 12:31 ` Ard Biesheuvel
2020-07-09 12:39 ` Ard Biesheuvel
2020-07-09 12:43 ` Will Deacon
2020-07-09 12:48 ` Alexandru Elisei
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=159369107379.3020197.4937110667602244064.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dave.martin@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@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).