linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vladimir Murzin <murzin.v@gmail.com>
Cc: paulus@samba.org, dborkman@redhat.com,
	linuxppc-dev@lists.ozlabs.org, davem@davemloft.net,
	Matt Evans <matt@ozlabs.org>
Subject: Re: [PATCH] ppc: bpf_jit: support MOD operation
Date: Tue, 03 Sep 2013 06:45:50 +1000	[thread overview]
Message-ID: <1378154750.3978.43.camel@pasglop> (raw)
In-Reply-To: <20130902174842.GA1866@hp530>

On Mon, 2013-09-02 at 19:48 +0200, Vladimir Murzin wrote:
> Ping
> 
> On Wed, Aug 28, 2013 at 02:49:52AM +0400, Vladimir Murzin wrote:
> > commit b6069a9570 (filter: add MOD operation) added generic
> > support for modulus operation in BPF.
> >
Sorry, nobody got a chance to review that yet. Unfortunately Matt
doesn't work for us anymore and none of us has experience with the
BPF code, so somebody (possibly me) will need to spend a bit of time
figuring it out before verifying that is correct.

Do you have a test case/suite by any chance ?

Ben.

> > This patch brings JIT support for PPC64
> > 
> > Signed-off-by: Vladimir Murzin <murzin.v@gmail.com>
> > ---
> >  arch/powerpc/net/bpf_jit_comp.c | 22 ++++++++++++++++++++++
> >  1 file changed, 22 insertions(+)
> > 
> > diff --git a/arch/powerpc/net/bpf_jit_comp.c b/arch/powerpc/net/bpf_jit_comp.c
> > index bf56e33..96f24dc 100644
> > --- a/arch/powerpc/net/bpf_jit_comp.c
> > +++ b/arch/powerpc/net/bpf_jit_comp.c
> > @@ -193,6 +193,28 @@ static int bpf_jit_build_body(struct sk_filter *fp, u32 *image,
> >  				PPC_MUL(r_A, r_A, r_scratch1);
> >  			}
> >  			break;
> > +		case BPF_S_ALU_MOD_X: /* A %= X; */
> > +			ctx->seen |= SEEN_XREG;
> > +			PPC_CMPWI(r_X, 0);
> > +			if (ctx->pc_ret0 != -1) {
> > +				PPC_BCC(COND_EQ, addrs[ctx->pc_ret0]);
> > +			} else {
> > +				PPC_BCC_SHORT(COND_NE, (ctx->idx*4)+12);
> > +				PPC_LI(r_ret, 0);
> > +				PPC_JMP(exit_addr);
> > +			}
> > +			PPC_DIVWU(r_scratch1, r_A, r_X);
> > +			PPC_MUL(r_scratch1, r_X, r_scratch1);
> > +			PPC_SUB(r_A, r_A, r_scratch1);
> > +			break;
> > +		case BPF_S_ALU_MOD_K: /* A %= K; */
> > +#define r_scratch2 (r_scratch1 + 1)
> > +			PPC_LI32(r_scratch2, K);
> > +			PPC_DIVWU(r_scratch1, r_A, r_scratch2);
> > +			PPC_MUL(r_scratch1, r_scratch2, r_scratch1);
> > +			PPC_SUB(r_A, r_A, r_scratch1);
> > +#undef r_scratch2
> > +			break;
> >  		case BPF_S_ALU_DIV_X: /* A /= X; */
> >  			ctx->seen |= SEEN_XREG;
> >  			PPC_CMPWI(r_X, 0);
> > -- 
> > 1.8.1.5
> > 

  reply	other threads:[~2013-09-02 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 22:49 [PATCH] ppc: bpf_jit: support MOD operation Vladimir Murzin
2013-09-02 17:48 ` Vladimir Murzin
2013-09-02 20:45   ` Benjamin Herrenschmidt [this message]
2013-09-03 19:58     ` Vladimir Murzin
2013-09-03 20:52       ` Daniel Borkmann
2013-09-04  7:04         ` Daniel Borkmann
2013-09-11 16:15           ` Vladimir Murzin
2013-09-12  1:18     ` Matt Evans
2013-09-12  2:56       ` Vladimir Murzin

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=1378154750.3978.43.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=matt@ozlabs.org \
    --cc=murzin.v@gmail.com \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).