From: Sandipan Das <sandipan@linux.ibm.com>
To: Jiong Wang <jiong.wang@netronome.com>
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org,
oss-drivers@netronome.com,
"Naveen N . Rao" <naveen.n.rao@linux.ibm.com>
Subject: Re: [PATCH bpf-next 2/7] ppc: bpf: implement jitting of BPF_ALU | BPF_ARSH | BPF_*
Date: Wed, 5 Dec 2018 12:07:54 +0530 [thread overview]
Message-ID: <7664a4d2-ed4e-4e60-2d1d-3b113d05972b@linux.ibm.com> (raw)
In-Reply-To: <1543956922-8620-3-git-send-email-jiong.wang@netronome.com>
Hi Jiong,
On 05/12/18 2:25 AM, Jiong Wang wrote:
> This patch implements code-gen for BPF_ALU | BPF_ARSH | BPF_*.
>
> Cc: Naveen N. Rao <naveen.n.rao@linux.ibm.com>
> Cc: Sandipan Das <sandipan@linux.ibm.com>
> Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
> ---
[...]
> diff --git a/arch/powerpc/net/bpf_jit_comp64.c b/arch/powerpc/net/bpf_jit_comp64.c
> index 17482f5..c685b4f 100644
> --- a/arch/powerpc/net/bpf_jit_comp64.c
> +++ b/arch/powerpc/net/bpf_jit_comp64.c
> @@ -529,9 +529,15 @@ static int bpf_jit_build_body(struct bpf_prog *fp, u32 *image,
> if (imm != 0)
> PPC_SRDI(dst_reg, dst_reg, imm);
> break;
> + case BPF_ALU | BPF_ARSH | BPF_X: /* (s32) dst >>= src */
> + PPC_SRAW(dst_reg, dst_reg, src_reg);
> + break;
On ppc64, the sraw and srawi instructions also use sign extension. So, you will have
to ensure that upper 32 bits are cleared. We already have a label in our JIT code
called bpf_alu32_trunc that takes care of this. Replacing the break statement with
a goto bpf_alu32_trunc will fix this.
> case BPF_ALU64 | BPF_ARSH | BPF_X: /* (s64) dst >>= src */
> PPC_SRAD(dst_reg, dst_reg, src_reg);
> break;
> + case BPF_ALU | BPF_ARSH | BPF_K: /* (s32) dst >>= imm */
> + PPC_SRAWI(dst_reg, dst_reg, imm);
> + break;
Same here.
> case BPF_ALU64 | BPF_ARSH | BPF_K: /* (s64) dst >>= imm */
> if (imm != 0)
> PPC_SRADI(dst_reg, dst_reg, imm);
>
With Regards,
Sandipan
next prev parent reply other threads:[~2018-12-05 6:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 20:55 [PATCH bpf-next 0/7] bpf: support BPF_ALU | BPF_ARSH Jiong Wang
2018-12-04 20:55 ` [PATCH bpf-next 1/7] mips: bpf: implement jitting of BPF_ALU | BPF_ARSH | BPF_X Jiong Wang
2018-12-05 0:02 ` Paul Burton
2018-12-05 11:07 ` Jiong Wang
2018-12-04 20:55 ` [PATCH bpf-next 2/7] ppc: bpf: implement jitting of BPF_ALU | BPF_ARSH | BPF_* Jiong Wang
2018-12-05 6:37 ` Sandipan Das [this message]
2018-12-05 11:28 ` Jiong Wang
2018-12-05 19:39 ` David Miller
2018-12-04 20:55 ` [PATCH bpf-next 3/7] s390: " Jiong Wang
2018-12-04 20:55 ` [PATCH bpf-next 4/7] nfp: " Jiong Wang
2018-12-04 20:55 ` [PATCH bpf-next 5/7] bpf: interpreter support BPF_ALU | BPF_ARSH Jiong Wang
2018-12-04 20:55 ` [PATCH bpf-next 6/7] bpf: verifier remove the rejection on " Jiong Wang
2018-12-04 20:55 ` [PATCH bpf-next 7/7] selftests: bpf: update testcases for " Jiong Wang
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=7664a4d2-ed4e-4e60-2d1d-3b113d05972b@linux.ibm.com \
--to=sandipan@linux.ibm.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jiong.wang@netronome.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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 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.