From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/bpf: use movn/movk/movk sequence to generate kernel addresses
Date: Tue, 27 Nov 2018 18:22:03 +0000 [thread overview]
Message-ID: <20181127182203.GA19721@arm.com> (raw)
In-Reply-To: <20181123172902.21480-1-ard.biesheuvel@linaro.org>
Hi Ard,
On Fri, Nov 23, 2018 at 06:29:02PM +0100, Ard Biesheuvel wrote:
> On arm64, all executable code is guaranteed to reside in the vmalloc
> space (or the module space), and so jump targets will only use 48
> bits at most, and the remaining bits are guaranteed to be 0x1.
>
> This means we can generate an immediate jump address using a sequence
> of one MOVN (move wide negated) and two MOVK instructions, where the
> first one sets the lower 16 bits but also sets all top bits to 0x1.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
Acked-by: Will Deacon <will.deacon@arm.com>
Denial, Alexei, shall I take this via arm64, or would you rather take
it via davem?
Cheers,
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
ast@fb.com, daniel@iogearbox.net
Subject: Re: [PATCH] arm64/bpf: use movn/movk/movk sequence to generate kernel addresses
Date: Tue, 27 Nov 2018 18:22:03 +0000 [thread overview]
Message-ID: <20181127182203.GA19721@arm.com> (raw)
In-Reply-To: <20181123172902.21480-1-ard.biesheuvel@linaro.org>
Hi Ard,
On Fri, Nov 23, 2018 at 06:29:02PM +0100, Ard Biesheuvel wrote:
> On arm64, all executable code is guaranteed to reside in the vmalloc
> space (or the module space), and so jump targets will only use 48
> bits at most, and the remaining bits are guaranteed to be 0x1.
>
> This means we can generate an immediate jump address using a sequence
> of one MOVN (move wide negated) and two MOVK instructions, where the
> first one sets the lower 16 bits but also sets all top bits to 0x1.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
Acked-by: Will Deacon <will.deacon@arm.com>
Denial, Alexei, shall I take this via arm64, or would you rather take
it via davem?
Cheers,
Will
next prev parent reply other threads:[~2018-11-27 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 17:29 [PATCH] arm64/bpf: use movn/movk/movk sequence to generate kernel addresses Ard Biesheuvel
2018-11-23 17:29 ` Ard Biesheuvel
2018-11-27 18:22 ` Will Deacon [this message]
2018-11-27 18:22 ` Will Deacon
2018-11-27 18:24 ` Daniel Borkmann
2018-11-27 18:24 ` Daniel Borkmann
2018-11-30 10:07 ` Daniel Borkmann
2018-11-30 10:07 ` Daniel Borkmann
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=20181127182203.GA19721@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.