From: matt <matt@localhost>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, matt@ozlabs.org, amodra@gmail.com
Subject: Re: [PATCH] powerpc: Fix BPF_JIT code to link with multiple TOCs
Date: Fri, 22 Jun 2012 09:58:43 +0100 [thread overview]
Message-ID: <74ade163faf9900aa58cd45d65643012@ozlabs.org> (raw)
In-Reply-To: <1340337027-22110-1-git-send-email-michael@ellerman.id.au>
On 2012-06-22 04:50, Michael Ellerman wrote:
> If the kernel is big enough (eg. allyesconfig), the linker may need
> to
> switch TOCs when calling from the BPF JIT code out to the external
> helpers (skb_copy_bits() & bpf_internal_load_pointer_neg_helper()).
>
> In order to do that we need to leave space after the bl for the
> linker
> to insert a reload of our TOC pointer.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Oops..!
Acked-by: Matt Evans <matt@ozlabs.org>
> ---
> arch/powerpc/net/bpf_jit_64.S | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/powerpc/net/bpf_jit_64.S
> b/arch/powerpc/net/bpf_jit_64.S
> index 55ba385..7d3a3b5 100644
> --- a/arch/powerpc/net/bpf_jit_64.S
> +++ b/arch/powerpc/net/bpf_jit_64.S
> @@ -105,6 +105,7 @@ sk_load_byte_msh_positive_offset:
> mr r4, r_addr; \
> li r6, SIZE; \
> bl skb_copy_bits; \
> + nop; \
> /* R3 = 0 on success */ \
> addi r1, r1, BPF_PPC_SLOWPATH_FRAME; \
> ld r0, 16(r1); \
> @@ -156,6 +157,7 @@ bpf_slow_path_byte_msh:
> mr r4, r_addr; \
> li r5, SIZE; \
> bl bpf_internal_load_pointer_neg_helper; \
> + nop; \
> /* R3 != 0 on success */ \
> addi r1, r1, BPF_PPC_SLOWPATH_FRAME; \
> ld r0, 16(r1); \
next prev parent reply other threads:[~2012-06-22 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 3:50 [PATCH] powerpc: Fix BPF_JIT code to link with multiple TOCs Michael Ellerman
2012-06-22 8:58 ` matt [this message]
2012-06-22 9:01 ` matt
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=74ade163faf9900aa58cd45d65643012@ozlabs.org \
--to=matt@localhost \
--cc=amodra@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).