From: Tom Musta <tommusta@gmail.com>
To: Alexander Graf <agraf@suse.de>,
Pierre Mallard <mallard.pierre@gmail.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 2/3] target-ppc : Add PPC_FLOAT_64 flag to instructions type
Date: Wed, 10 Sep 2014 11:23:59 -0500 [thread overview]
Message-ID: <54107B1F.4040805@gmail.com> (raw)
In-Reply-To: <5410175B.5010107@suse.de>
On 9/10/2014 4:18 AM, Alexander Graf wrote:
>
>
> On 10.09.14 07:03, Pierre Mallard wrote:
>> This patch declare a new floating point instruction flag PPC_FLOAT_64 to be used
>> by fcfid, fctid[z] operations. Note that due to limited number of bit,
>> FSEL and FRES points now to same value, and PPC_FLOAT_64 to former FSEL value.
>> (There seems to be no case where FSEL and FRES are not used together at the moment)
>>
>> Signed-off-by: Pierre Mallard <mallard.pierre@gmail.com>
>> ---
>> target-ppc/cpu.h | 7 +++++--
>> target-ppc/translate_init.c | 2 +-
>> 2 files changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/target-ppc/cpu.h b/target-ppc/cpu.h
>> index b64c652..b5b3912 100644
>> --- a/target-ppc/cpu.h
>> +++ b/target-ppc/cpu.h
>> @@ -1868,9 +1868,12 @@ enum {
>> PPC_FLOAT_FRES = 0x0000000000080000ULL,
>> PPC_FLOAT_FRSQRTE = 0x0000000000100000ULL,
>> PPC_FLOAT_FRSQRTES = 0x0000000000200000ULL,
>> - PPC_FLOAT_FSEL = 0x0000000000400000ULL,
>> + PPC_FLOAT_FSEL = 0x0000000000080000ULL,
>> PPC_FLOAT_STFIWX = 0x0000000000800000ULL,
>>
>> + /* Use for PPC with double precision fpu */
>> + PPC_FLOAT_64 = 0x0000000000400000ULL,
>
> Please keep the list sorted by the bit number. Also I think we're better
> off not having the same bit used for 2 enums. Just keep PPC_FLOAT_FRES
> and make FSEL depend on the FRES bit in translate.c
>
Alternatively, you could add the new flag to PPC2_xxx .
>> +
>> /* Vector/SIMD extensions */
>> /* Altivec support */
>> PPC_ALTIVEC = 0x0000000001000000ULL,
>> @@ -1957,7 +1960,7 @@ enum {
>> | PPC_STRING | PPC_FLOAT | PPC_FLOAT_EXT \
>> | PPC_FLOAT_FSQRT | PPC_FLOAT_FRES \
>> | PPC_FLOAT_FRSQRTE | PPC_FLOAT_FRSQRTES \
>> - | PPC_FLOAT_FSEL | PPC_FLOAT_STFIWX \
>> + | PPC_FLOAT_FSEL | PPC_FLOAT_STFIWX | PPC_FLOAT_64 \
>> | PPC_ALTIVEC | PPC_SPE | PPC_SPE_SINGLE \
>> | PPC_SPE_DOUBLE | PPC_MEM_TLBIA \
>> | PPC_MEM_TLBIE | PPC_MEM_TLBSYNC \
>> diff --git a/target-ppc/translate_init.c b/target-ppc/translate_init.c
>> index b4dedce..073bef1 100644
>> --- a/target-ppc/translate_init.c
>> +++ b/target-ppc/translate_init.c
>> @@ -3899,7 +3899,7 @@ POWERPC_FAMILY(440x5)(ObjectClass *oc, void *data)
>> pcc->insns_flags = PPC_INSNS_BASE | PPC_STRING |
>> #ifdef PPC440x5_HAVE_FPU
>> PPC_FLOAT | PPC_FLOAT_FSQRT |
>> - PPC_FLOAT_STFIWX |
>> + PPC_FLOAT_STFIWX | PPC_FLOAT_64 |
>> #endif
>> PPC_DCR | PPC_WRTEE | PPC_RFMCI |
>> PPC_CACHE | PPC_CACHE_ICBI |
>>
next prev parent reply other threads:[~2014-09-10 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 5:03 [Qemu-devel] [PATCH 0/3] Enabling floating point instruction to 440x5 CPUs Pierre Mallard
2014-09-10 5:03 ` [Qemu-devel] [PATCH 1/3] target-ppc : Add floating point ability to 440x5 PPC CPU Pierre Mallard
2014-09-10 9:13 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-09-10 5:03 ` [Qemu-devel] [PATCH 2/3] target-ppc : Add PPC_FLOAT_64 flag to instructions type Pierre Mallard
2014-09-10 9:18 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-09-10 16:23 ` Tom Musta [this message]
2014-09-10 5:03 ` [Qemu-devel] [PATCH 3/3] target-ppc : Add PPC_FLOAT_64 type to fctid, fctidz and fcfid and remove their TARGET_PPC64 restriction Pierre Mallard
2014-09-10 9:19 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-09-10 16:44 ` Tom Musta
2014-09-10 9:20 ` [Qemu-devel] [Qemu-ppc] [PATCH 0/3] Enabling floating point instruction to 440x5 CPUs Alexander Graf
2014-09-10 17:15 ` Tom Musta
2014-09-10 18:02 ` Pierre Mallard
2014-09-10 22:43 ` Pierre Mallard
2014-09-11 12:30 ` Tom Musta
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=54107B1F.4040805@gmail.com \
--to=tommusta@gmail.com \
--cc=agraf@suse.de \
--cc=mallard.pierre@gmail.com \
--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).