From: Balbir Singh <bsingharora@gmail.com>
To: Matt Brown <matthew.brown.dev@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 2/5] powerpc/lib/sstep: Add popcnt instruction emulation
Date: Tue, 25 Jul 2017 17:12:31 +1000 [thread overview]
Message-ID: <1500966751.2611.1.camel@gmail.com> (raw)
In-Reply-To: <20170725033320.17893-2-matthew.brown.dev@gmail.com>
On Tue, 2017-07-25 at 13:33 +1000, Matt Brown wrote:
> This adds emulations for the popcntb, popcntw, and popcntd instructions.
> Tested for correctness against the popcnt{b,w,d} instructions on ppc64le.
>
> Signed-off-by: Matt Brown <matthew.brown.dev@gmail.com>
> ---
> v3:
> - optimised using the Giles-Miller method of side-ways addition
> v2:
> - fixed opcodes
> - fixed typecasting
> - fixed bitshifting error for both 32 and 64bit arch
> ---
> arch/powerpc/lib/sstep.c | 40 +++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 39 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/lib/sstep.c b/arch/powerpc/lib/sstep.c
> index 87d277f..c1f9cdb 100644
> --- a/arch/powerpc/lib/sstep.c
> +++ b/arch/powerpc/lib/sstep.c
> @@ -612,6 +612,32 @@ static nokprobe_inline void do_cmpb(struct pt_regs *regs, unsigned long v1,
> regs->gpr[rd] = out_val;
> }
>
> +/*
> + * The size parameter is used to adjust the equivalent popcnt instruction.
> + * popcntb = 8, popcntw = 32, popcntd = 64
> + */
> +static nokprobe_inline void do_popcnt(struct pt_regs *regs, unsigned long v1,
> + int size, int ra)
> +{
> + unsigned long long out = v1;
> +
> + out = (0x5555555555555555 & out) + (0x5555555555555555 & (out >> 1));
> + out = (0x3333333333333333 & out) + (0x3333333333333333 & (out >> 2));
> + out = (0x0f0f0f0f0f0f0f0f & out) + (0x0f0f0f0f0f0f0f0f & (out >> 4));
> + if (size == 8) { /* popcntb */
> + regs->gpr[ra] = out;
> + return;
> + }
> + out = (0x001f001f001f001f & out) + (0x001f001f001f001f & (out >> 8));
Why are we using 0x001f001f here? Now that we've got things in the
bytes with 0's prefixing, we can directly use
out = out + out >> 8
> + out = (0x0000003f0000003f & out) + (0x0000003f0000003f & (out >> 16));
Same as above
> + if (size == 32) { /* popcntw */
> + regs->gpr[ra] = out;
> + return;
> + }
> + out = (0x000000000000007f & out) + (0x000000000000007f & (out >> 32));
> + regs->gpr[ra] = out; /* popcntd */
Ditto
Otherwise looks good!
Balbir Singh.
next prev parent reply other threads:[~2017-07-25 7:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 3:33 [PATCH v3 1/5] powerpc/lib/sstep: Add cmpb instruction emulation Matt Brown
2017-07-25 3:33 ` [PATCH v3 2/5] powerpc/lib/sstep: Add popcnt " Matt Brown
2017-07-25 7:12 ` Balbir Singh [this message]
2017-07-25 10:24 ` David Laight
2017-07-25 13:32 ` Balbir Singh
2017-07-26 7:29 ` Gabriel Paubert
2017-07-25 3:33 ` [PATCH v3 3/5] powerpc/lib/sstep: Add bpermd " Matt Brown
2017-07-25 3:33 ` [PATCH v3 4/5] powerpc/lib/sstep: Add prty " Matt Brown
2017-07-25 8:08 ` Balbir Singh
2017-07-26 7:49 ` Gabriel Paubert
2017-07-25 15:30 ` Segher Boessenkool
2017-07-26 10:03 ` Michael Ellerman
2017-07-26 16:02 ` Segher Boessenkool
2017-07-27 1:26 ` Michael Ellerman
2017-07-28 0:48 ` Matt Brown
2017-07-28 1:31 ` Michael Ellerman
2017-07-25 3:33 ` [PATCH v3 5/5] powerpc/lib/sstep: Add isel " Matt Brown
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=1500966751.2611.1.camel@gmail.com \
--to=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew.brown.dev@gmail.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 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).