From: joserz@linux.vnet.ibm.com
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, bharata@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2 0/4] POWER9 TCG enablements - BCD functions part II
Date: Thu, 24 Nov 2016 14:36:11 -0200 [thread overview]
Message-ID: <20161124163611.GB5922@pacoca> (raw)
In-Reply-To: <20161124012832.GQ17795@umbus.fritz.box>
David,
Thank you again for reviewing my code, I'm making the changes. I only have a question about patch 1/4 which I didn't find the issue so I'm waiting for Richard's answer.
Thanks!
On Thu, Nov 24, 2016 at 12:28:32PM +1100, David Gibson wrote:
> On Wed, Nov 23, 2016 at 02:21:41PM -0200, Jose Ricardo Ziviani wrote:
> > v2:
> > - use div128 and mul64 functions to make code easier to understand
> > - fixed int128 neg
> > - improved functions bcdcpsgn and bcdsetsgn to do less work
> > than necessary
> > - rebased on ppc-for-2.9
> >
> > This serie contains 4 new instructions for POWER9 ISA3.0
> >
> > bcdcfsq.: Convert signed quadword to packed BCD
> > bcdctsq.: Convert packed BCD to signed quadword
> > bcdcpsgn.: Copy the sign of a register to another
> > bcdsetsgn.: Set the BCD sign according to a preferred sign
>
> Patch 1/4 has some problems, see comments.
>
> Patches 2..4/4 look ok - except that they'll need to be updated for
> the recent change I merged from Nikunj (in ppc-for-2.9) which changes
> the meaning of CRF_*.
>
> >
> > Jose Ricardo Ziviani (4):
> > target-ppc: Implement bcdcfsq. instruction
> > target-ppc: Implement bcdctsq. instruction
> > target-ppc: Implement bcdcpsgn. instruction
> > target-ppc: Implement bcdsetsgn. instruction
> >
> > target-ppc/helper.h | 4 ++
> > target-ppc/int_helper.c | 127 ++++++++++++++++++++++++++++++++++++
> > target-ppc/translate/vmx-impl.inc.c | 25 +++++++
> > target-ppc/translate/vmx-ops.inc.c | 2 +-
> > 4 files changed, 157 insertions(+), 1 deletion(-)
> >
>
> --
> David Gibson | I'll have my music baroque, and my code
> david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
> | _way_ _around_!
> http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2016-11-24 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 16:21 [Qemu-devel] [PATCH v2 0/4] POWER9 TCG enablements - BCD functions part II Jose Ricardo Ziviani
2016-11-23 16:21 ` [Qemu-devel] [PATCH v2 1/4] target-ppc: Implement bcdcfsq. instruction Jose Ricardo Ziviani
2016-11-24 0:43 ` Richard Henderson
2016-11-24 1:20 ` David Gibson
2016-11-24 16:31 ` [Qemu-devel] [Qemu-ppc] " joserz
2016-11-24 22:16 ` David Gibson
2016-11-24 1:18 ` [Qemu-devel] " David Gibson
2016-11-23 16:21 ` [Qemu-devel] [PATCH v2 2/4] target-ppc: Implement bcdctsq. instruction Jose Ricardo Ziviani
2016-11-24 1:24 ` David Gibson
2016-11-23 16:21 ` [Qemu-devel] [PATCH v2 3/4] target-ppc: Implement bcdcpsgn. instruction Jose Ricardo Ziviani
2016-11-24 1:26 ` David Gibson
2016-11-23 16:21 ` [Qemu-devel] [PATCH v2 4/4] target-ppc: Implement bcdsetsgn. instruction Jose Ricardo Ziviani
2016-11-24 1:27 ` David Gibson
2016-11-24 1:28 ` [Qemu-devel] [PATCH v2 0/4] POWER9 TCG enablements - BCD functions part II David Gibson
2016-11-24 16:36 ` joserz [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=20161124163611.GB5922@pacoca \
--to=joserz@linux.vnet.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).