From: Cedric Le Goater <clg@fr.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: "list@suse.de:PowerPC" <qemu-ppc@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-ppc: add extended opcodes for dcbt
Date: Thu, 20 Feb 2014 14:09:11 +0100 [thread overview]
Message-ID: <5305FE77.30208@fr.ibm.com> (raw)
In-Reply-To: <38624BCC-C1F3-433F-8BA2-5AC6A0A8007B@suse.de>
On 02/20/2014 02:07 PM, Alexander Graf wrote:
>
> On 20.02.2014, at 14:01, Cédric Le Goater <clg@fr.ibm.com> wrote:
>
>> The latest glibc provides a memrchr routine using an extended opcode
>> of the 'dcbt' instruction :
>>
>> 00000000000a7cc0 <memrchr>:
>> a7cc0: 11 00 4c 3c addis r2,r12,17
>> a7cc4: b8 f8 42 38 addi r2,r2,-1864
>> a7cc8: 14 2a e3 7c add r7,r3,r5
>> a7ccc: d0 00 07 7c neg r0,r7
>> a7cd0: ff ff e7 38 addi r7,r7,-1
>> a7cd4: 78 1b 6a 7c mr r10,r3
>> a7cd8: 24 06 e6 78 rldicr r6,r7,0,56
>> a7cdc: 60 00 20 39 li r9,96
>> a7ce0: 2c 32 09 7e dcbtt r9,r6
>> ....
>>
>> which breaks grep, and other commands, in TCG mode :
>>
>> invalid bits: 02000000 for opcode: 1f - 16 - 08 (7e09322c) 00003fff799feca0
>>
>> This patch adds the extended opcodes as no-ops just like the 'dcbt'
>> instruction. Other 'dcb*' instructions might be impacted but they
>> have not showed up yet.
>>
>> Signed-off-by: Cédric Le Goater <clg@fr.ibm.com>
>
> Please also remove the 0x02 bit from dcbtst. I don't see anything in 2.07
> indicating that that bit should be reserved and I prefer to have those two
> instructions be consistent with each other.
ok. I will send a v2.
Thanks,
C.
next prev parent reply other threads:[~2014-02-20 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 13:01 [Qemu-devel] [PATCH] target-ppc: add extended opcodes for dcbt Cédric Le Goater
2014-02-20 13:07 ` Alexander Graf
2014-02-20 13:09 ` Cedric Le Goater [this message]
2014-02-20 13:20 ` [Qemu-devel] [PATCH v2] target-ppc: add extended opcodes for dcbt/dcbtst Cédric Le Goater
2014-02-20 13:23 ` Alexander Graf
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=5305FE77.30208@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=agraf@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.