From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/8] arm64: alternative: Add support for patching adrp instructions
Date: Mon, 22 Aug 2016 12:19:22 +0100 [thread overview]
Message-ID: <20160822111921.GC14680@arm.com> (raw)
In-Reply-To: <1471525832-21209-6-git-send-email-suzuki.poulose@arm.com>
On Thu, Aug 18, 2016 at 02:10:29PM +0100, Suzuki K Poulose wrote:
> adrp uses PC-relative address offset to a page (of 4K size) of
> a symbol. If it appears in an alternative code patched in, we
> should adjust the offset to reflect the address where it will
> be run from. This patch adds support for fixing the offset
> for adrp instructions.
>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Andre Przywara <andre.przywara@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> ---
> arch/arm64/kernel/alternative.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/kernel/alternative.c b/arch/arm64/kernel/alternative.c
> index d2ee1b2..71c6962 100644
> --- a/arch/arm64/kernel/alternative.c
> +++ b/arch/arm64/kernel/alternative.c
> @@ -80,6 +80,19 @@ static u32 get_alt_insn(struct alt_instr *alt, u32 *insnptr, u32 *altinsnptr)
> offset = target - (unsigned long)insnptr;
> insn = aarch64_set_branch_offset(insn, offset);
> }
> + } else if (aarch64_insn_is_adrp(insn)) {
> + s32 orig_offset, new_offset;
> + unsigned long target;
> +
> + /*
> + * If we're replacing an adrp instruction, which uses PC-relative
> + * immediate addressing, adjust the offset to reflect the new
> + * PC. adrp operates on 4K aligned addresses.
> + */
> + orig_offset = aarch64_insn_adrp_get_offset(insn);
> + target = ((unsigned long)altinsnptr & ~0xfffUL) + orig_offset;
> + new_offset = target - ((unsigned long)insnptr & ~0xfffUL);
The masking with ~0xfffUL might be nicer if you write it as
align_down(ptr, SZ_4K);
> + insn = aarch64_insn_adrp_set_offset(insn, new_offset);
> }
>
> return insn;
I wonder if we shouldn't have a catch-all for any instructions performing
PC-relative operations here, because silent corruption of the instruction
stream is pretty horrible. What other instructions are there? ADR, LDR
(literal), ... ?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
mark.rutland@arm.com, andre.przywara@arm.com,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH 5/8] arm64: alternative: Add support for patching adrp instructions
Date: Mon, 22 Aug 2016 12:19:22 +0100 [thread overview]
Message-ID: <20160822111921.GC14680@arm.com> (raw)
In-Reply-To: <1471525832-21209-6-git-send-email-suzuki.poulose@arm.com>
On Thu, Aug 18, 2016 at 02:10:29PM +0100, Suzuki K Poulose wrote:
> adrp uses PC-relative address offset to a page (of 4K size) of
> a symbol. If it appears in an alternative code patched in, we
> should adjust the offset to reflect the address where it will
> be run from. This patch adds support for fixing the offset
> for adrp instructions.
>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Andre Przywara <andre.przywara@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> ---
> arch/arm64/kernel/alternative.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/kernel/alternative.c b/arch/arm64/kernel/alternative.c
> index d2ee1b2..71c6962 100644
> --- a/arch/arm64/kernel/alternative.c
> +++ b/arch/arm64/kernel/alternative.c
> @@ -80,6 +80,19 @@ static u32 get_alt_insn(struct alt_instr *alt, u32 *insnptr, u32 *altinsnptr)
> offset = target - (unsigned long)insnptr;
> insn = aarch64_set_branch_offset(insn, offset);
> }
> + } else if (aarch64_insn_is_adrp(insn)) {
> + s32 orig_offset, new_offset;
> + unsigned long target;
> +
> + /*
> + * If we're replacing an adrp instruction, which uses PC-relative
> + * immediate addressing, adjust the offset to reflect the new
> + * PC. adrp operates on 4K aligned addresses.
> + */
> + orig_offset = aarch64_insn_adrp_get_offset(insn);
> + target = ((unsigned long)altinsnptr & ~0xfffUL) + orig_offset;
> + new_offset = target - ((unsigned long)insnptr & ~0xfffUL);
The masking with ~0xfffUL might be nicer if you write it as
align_down(ptr, SZ_4K);
> + insn = aarch64_insn_adrp_set_offset(insn, new_offset);
> }
>
> return insn;
I wonder if we shouldn't have a catch-all for any instructions performing
PC-relative operations here, because silent corruption of the instruction
stream is pretty horrible. What other instructions are there? ADR, LDR
(literal), ... ?
Will
next prev parent reply other threads:[~2016-08-22 11:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 13:10 [RESEND] [PATCH 0/8] arm64: Work around for mismatched cache line size Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-18 13:10 ` [PATCH 1/8] arm64: Set the safe value for L1 icache policy Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-18 13:10 ` [PATCH 2/8] arm64: Use consistent naming for errata handling Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-18 13:10 ` [PATCH 3/8] arm64: Rearrange CPU errata workaround checks Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-18 13:10 ` [PATCH 4/8] arm64: insn: Add helpers for adrp offsets Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-18 14:47 ` Marc Zyngier
2016-08-18 14:47 ` Marc Zyngier
2016-08-18 14:52 ` Suzuki K Poulose
2016-08-18 14:52 ` Suzuki K Poulose
2016-08-18 13:10 ` [PATCH 5/8] arm64: alternative: Add support for patching adrp instructions Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-22 11:19 ` Will Deacon [this message]
2016-08-22 11:19 ` Will Deacon
2016-08-23 9:39 ` Suzuki K Poulose
2016-08-23 9:39 ` Suzuki K Poulose
2016-08-22 11:45 ` Ard Biesheuvel
2016-08-22 11:45 ` Ard Biesheuvel
2016-08-23 9:16 ` Suzuki K Poulose
2016-08-23 9:16 ` Suzuki K Poulose
2016-08-23 11:32 ` Ard Biesheuvel
2016-08-23 11:32 ` Ard Biesheuvel
2016-08-18 13:10 ` [PATCH 6/8] arm64: Introduce raw_{d,i}cache_line_size Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-18 17:57 ` Geoff Levand
2016-08-18 17:57 ` Geoff Levand
2016-08-22 10:00 ` Will Deacon
2016-08-22 10:00 ` Will Deacon
2016-08-23 10:07 ` Suzuki K Poulose
2016-08-23 10:07 ` Suzuki K Poulose
2016-08-18 13:10 ` [PATCH 7/8] arm64: Refactor sysinstr exception handling Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-22 12:53 ` Will Deacon
2016-08-22 12:53 ` Will Deacon
2016-08-23 10:19 ` Suzuki K Poulose
2016-08-23 10:19 ` Suzuki K Poulose
2016-08-18 13:10 ` [PATCH 8/8] arm64: Work around systems with mismatched cache line sizes Suzuki K Poulose
2016-08-18 13:10 ` Suzuki K Poulose
2016-08-22 13:02 ` Will Deacon
2016-08-22 13:02 ` Will Deacon
2016-08-24 13:23 ` Suzuki K Poulose
2016-08-24 13:23 ` Suzuki K Poulose
-- strict thread matches above, loose matches on Subject: below --
2016-07-08 11:37 [PATCH 0/8] arm64: Work around for mismatched cache line size Suzuki K Poulose
2016-07-08 11:37 ` [PATCH 5/8] arm64: alternative: Add support for patching adrp instructions Suzuki K Poulose
2016-07-08 11:37 ` Suzuki K Poulose
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=20160822111921.GC14680@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.