From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Olof Johansson <olof@lixom.net>
Cc: Network Development <netdev@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH net-next 13/13] ARM: net: bpf: use double-word load/stores where available
Date: Tue, 10 Jul 2018 18:14:38 +0100 [thread overview]
Message-ID: <20180710171438.GM17271@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAOesGMio4JTzAPQ3Bkx8LxhkhJStzOGC6t2U8aC6m4TiBtaunQ@mail.gmail.com>
On Tue, Jul 10, 2018 at 10:03:33AM -0700, Olof Johansson wrote:
> Hi Russell,
> > @@ -663,13 +679,27 @@ static inline void emit_a32_mov_r(const s8 dst, const s8 src,
> > static inline void emit_a32_mov_r64(const bool is64, const s8 dst[],
> > const s8 src[],
> > struct jit_ctx *ctx) {
> > - emit_a32_mov_r(dst_lo, src_lo, ctx);
> > - if (is64) {
> > + if (!is64) {
> > + emit_a32_mov_r(dst_lo, src_lo, ctx);
> > + /* Zero out high 4 bytes */
> > + emit_a32_mov_i(dst_hi, 0, ctx);
> > + } else if (__LINUX_ARM_ARCH__ < 6 &&
> > + ctx->cpu_architecture < CPU_ARCH_ARMv5) {
> > /* complete 8 byte move */
> > + emit_a32_mov_r(dst_lo, src_lo, ctx);
> > emit_a32_mov_r(dst_hi, src_hi, ctx);
>
>
> Tiny nit: Looks like you compare for >= ARMv5TE above and <ARMv5 here.
Good catch, I'll fix it, and it gives me some satisfaction that
someone is reviewing this JIT code closely! IMHO, JITs need a lot
of scrutiny.
> I'm not aware of any vanilla v5 implementations (all I can find are
> v5TE or <=v4T), so it doesn't seem like something actually causing
> problems. Mostly pointing it out for consistency's sake.
They're rare - I think the only one is an ARM1020 (ARMv5T) as opposed
to the ARM1020E (ARMv5TE). Whether any are in the wild or not is
another matter.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 13.8Mbps down 630kbps up
According to speedtest.net: 13Mbps down 490kbps up
prev parent reply other threads:[~2018-07-10 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 12:33 [PATCH 00/13] ARM BPF jit compiler improvements Russell King - ARM Linux
2018-07-10 12:36 ` [PATCH net-next 01/13] ARM: net: bpf: enumerate the JIT scratch stack layout Russell King
2018-07-10 18:30 ` Daniel Borkmann
2018-07-10 21:57 ` Russell King - ARM Linux
2018-07-10 12:36 ` [PATCH net-next 02/13] ARM: net: bpf: provide load/store ops with negative immediates Russell King
2018-07-10 12:36 ` [PATCH net-next 03/13] ARM: net: bpf: use negative numbers for stacked registers Russell King
2018-07-10 12:36 ` [PATCH net-next 04/13] ARM: net: bpf: remove is_on_stack() and sstk/dstk Russell King
2018-07-10 12:36 ` [PATCH net-next 05/13] ARM: net: bpf: provide accessor functions for BPF registers Russell King
2018-07-10 12:36 ` [PATCH net-next 06/13] ARM: net: bpf: 64-bit " Russell King
2018-07-10 12:36 ` [PATCH net-next 07/13] ARM: net: bpf: access eBPF scratch space using ARM FP register Russell King
2018-07-10 12:36 ` [PATCH net-next 08/13] ARM: net: bpf: use immediate forms of instructions where possible Russell King
2018-07-10 19:12 ` kbuild test robot
2018-07-10 12:36 ` [PATCH net-next 09/13] ARM: net: bpf: use ldr instructions with shifted rm register Russell King
2018-07-10 12:36 ` [PATCH net-next 10/13] ARM: net: bpf: avoid reloading 'index' Russell King
2018-07-10 12:37 ` [PATCH net-next 11/13] ARM: net: bpf: avoid reloading 'array' Russell King
2018-07-10 12:37 ` [PATCH net-next 12/13] ARM: net: bpf: always use odd/even register pair Russell King
2018-07-10 12:37 ` [PATCH net-next 13/13] ARM: net: bpf: use double-word load/stores where available Russell King
2018-07-10 17:03 ` Olof Johansson
2018-07-10 17:14 ` Russell King - ARM Linux [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=20180710171438.GM17271@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=daniel@iogearbox.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
/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).