[Qemu-devel] mfocrf missing on e500v2

[Qemu-devel] mfocrf missing on e500v2

[Alexander Graf]

Hi Richard,

I've finally managed to check out why my e500v2 automated tests fail to
run. Apparently they break because autotest wants to execute target code
and runs into an illegal instruction while doing that:

Program received signal SIGILL, Illegal instruction.
0xb57c84cc in ?? ()
(gdb) x /i $pc
=> 0xb57c84cc:	mfocrf  r0,1

And lo and behold, I really couldn't find any reference to mfocrf in the
e500v2 spec.

Is there any way to disable setcond2 for those chips?


Alex

Re: [Qemu-devel] mfocrf missing on e500v2

[Maciej W. Rozycki]

On Fri, 6 Mar 2015, Alexander Graf wrote:

> I've finally managed to check out why my e500v2 automated tests fail to
> run. Apparently they break because autotest wants to execute target code
> and runs into an illegal instruction while doing that:
> 
> Program received signal SIGILL, Illegal instruction.
> 0xb57c84cc in ?? ()
> (gdb) x /i $pc
> => 0xb57c84cc:	mfocrf  r0,1
> 
> And lo and behold, I really couldn't find any reference to mfocrf in the
> e500v2 spec.

 Do real e500 processors trap on this operation as well?  Here's what 
the Power ISA [1] says on the mtocrf and mfocrf instructions:

"These forms of the mtcrf and mfcr instructions are intended to replace 
the old forms of the instructions (the forms shown in page 102), which 
will eventually be phased out of the architecture. The new forms are 
backward compatible with most processors that comply with versions of 
the architecture that precede Version 2.00.  On those processors, the 
new forms are treated as the old forms.

"However, on some processors that comply with versions of the 
architecture that precede Version 2.00 the new forms may be treated as 
follows:

mtocrf: may cause the system illegal instruction error handler to be 
        invoked

mfocrf: may place an undefined value into register RT"

So it looks to me like the ISA, for its extension, relies on partial 
instruction decoding here.

 Furthermore both the opcode and the extended opcode are the same for 
each of mtcrf/mtocrf and mfcr/mfocrf, and the instructions within these 
pairs only differ by the value of a single bit within a field used for 
RA by operations that use it.  That bit is specified as reserved (/) for 
mtcrf/mfcr by e500 processor documentation [2][3][4] and likely a "don't 
care" in real implementations.  Offhand I suspect this is what pre-2.00 
ISA revisions did too.

 So perhaps the partial decoding of mtcrf and mfcr has to be implemented 
in QEMU for the processors concerned instead then?  The answer will 
depend on what actual hardware does.

References:

[1] "Power ISA", IBM Corporation, Version 2.06 Revision B, July 23, 
    2010, Section 3.3.15.1 "Move To/From One Condition Register Field 
    Instructions", p. 103

[2] "PowerPC e500 Core Family Reference Manual", Freescale 
    Semiconductor, Document ID: E500CORERM, Rev. 1, 4/2005, Table D-1 
    "Instructions (Binary) by Mnemonic", p. D-17

[3] same, Table D-2 "Instructions (Decimal and Hexadecimal) by Opcode",
    p. D-32

[4] same, Table D-3 "Instructions (Binary) by Form", pp. D-37, D-48

  Maciej

Re: [Qemu-devel] mfocrf missing on e500v2

[Alexander Graf]

> Am 06.03.2015 um 18:20 schrieb Maciej W. Rozycki <macro@linux-mips.org>:
> 
>> On Fri, 6 Mar 2015, Alexander Graf wrote:
>> 
>> I've finally managed to check out why my e500v2 automated tests fail to
>> run. Apparently they break because autotest wants to execute target code
>> and runs into an illegal instruction while doing that:
>> 
>> Program received signal SIGILL, Illegal instruction.
>> 0xb57c84cc in ?? ()
>> (gdb) x /i $pc
>> => 0xb57c84cc:    mfocrf  r0,1
>> 
>> And lo and behold, I really couldn't find any reference to mfocrf in the
>> e500v2 spec.
> 
> Do real e500 processors trap on this operation as well?  

The illegal instruction I posted about above was when running qemu *on* e500v2, because TCG emits mfocrf ;).


Alex

Re: [Qemu-devel] mfocrf missing on e500v2

[Maciej W. Rozycki]

On Fri, 6 Mar 2015, Alexander Graf wrote:

> >> And lo and behold, I really couldn't find any reference to mfocrf in the
> >> e500v2 spec.
> > 
> > Do real e500 processors trap on this operation as well?  
> 
> The illegal instruction I posted about above was when running qemu 
> *on* e500v2, because TCG emits mfocrf ;).

 Ah OK, fair enough!  I guess that answers the question.

  Maciej

Re: [Qemu-devel] mfocrf missing on e500v2

[Richard Henderson]

On 03/06/2015 08:04 AM, Alexander Graf wrote:
> Hi Richard,
> 
> I've finally managed to check out why my e500v2 automated tests fail to
> run. Apparently they break because autotest wants to execute target code
> and runs into an illegal instruction while doing that:
> 
> Program received signal SIGILL, Illegal instruction.
> 0xb57c84cc in ?? ()
> (gdb) x /i $pc
> => 0xb57c84cc:	mfocrf  r0,1
> 
> And lo and behold, I really couldn't find any reference to mfocrf in the
> e500v2 spec.
> 
> Is there any way to disable setcond2 for those chips?

No, not disable setcond2.

But the proper solution is to emit mfcrf (i.e. all of the cr regs, not "one" of
the cregs).  We'd want to check the processor we're running on, since
mfcrf is slower than mfocrf on modern hardware.  Can you see if there's a
bit in AT_HWCAP that covers this?


r~