From: murzin.v@gmail.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: bpf_jit: support MOD operation
Date: Mon, 2 Sep 2013 19:49:32 +0200 [thread overview]
Message-ID: <20130902174928.GB1866@hp530> (raw)
In-Reply-To: <1377643952-10388-1-git-send-email-murzin.v@gmail.com>
Ping
On Wed, Aug 28, 2013 at 02:52:32AM +0400, Vladimir Murzin wrote:
> commit b6069a9570 (filter: add MOD operation) added generic
> support for modulus operation in BPF.
>
> This patch brings JIT support for ARM.
>
> Signed-off-by: Vladimir Murzin <murzin.v@gmail.com>
> ---
> arch/arm/net/bpf_jit_32.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm/net/bpf_jit_32.c b/arch/arm/net/bpf_jit_32.c
> index f50d223..0bfff55 100644
> --- a/arch/arm/net/bpf_jit_32.c
> +++ b/arch/arm/net/bpf_jit_32.c
> @@ -636,6 +636,24 @@ load_ind:
> update_on_xread(ctx);
> emit(ARM_MUL(r_A, r_A, r_X), ctx);
> break;
> + case BPF_S_ALU_MOD_X: /* A %= X; */
> + update_on_xread(ctx);
> + emit(ARM_CMP_I(r_X, 0), ctx);
> + emit_err_ret(ARM_COND_EQ, ctx);
> + emit_udiv(r_scratch, r_A, r_X, ctx);
> + emit(ARM_MUL(r_scratch, r_X, r_scratch), ctx);
> + emit(ARM_SUB_R(r_A, r_A, r_scratch), ctx);
> + break;
> + case BPF_S_ALU_MOD_K: /* A %= K; */
> + /*
> + * reuse ARM_R1 as the temp register - it should be safe
> + * as soon as udiv may touch it too.
> + */
> + emit_mov_i(ARM_R1, k, ctx);
> + emit_udiv(r_scratch, r_A, ARM_R1, ctx);
> + emit(ARM_MUL(r_scratch, ARM_R1, r_scratch), ctx);
> + emit(ARM_SUB_R(r_A, r_A, r_scratch), ctx);
> + break;
> case BPF_S_ALU_DIV_K:
> /* current k == reciprocal_value(userspace k) */
> emit_mov_i(r_scratch, k, ctx);
> --
> 1.8.1.5
>
prev parent reply other threads:[~2013-09-02 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 22:52 [PATCH] arm: bpf_jit: support MOD operation Vladimir Murzin
2013-09-02 17:49 ` Vladimir Murzin [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=20130902174928.GB1866@hp530 \
--to=murzin.v@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox