Re: [PATCH qemu v19] spapr: Implement Open Firmware client interface

[Alexey Kardashevskiy]

On 18/05/2021 04:44, BALATON Zoltan wrote:
> On Mon, 17 May 2021, BALATON Zoltan wrote:
> > On Mon, 17 May 2021, Alexey Kardashevskiy wrote:
> > > On 5/17/21 09:34, BALATON Zoltan wrote:
> > > > On Sat, 15 May 2021, BALATON Zoltan wrote:
> > > > > On Sat, 15 May 2021, BALATON Zoltan wrote:
> > > > > > On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
> > >
> > > [snip]


> invalid/unsupported opcode: 3e - 08 - 1e - 01 (f821ff91) 00000120 0
> ----------------
> IN:
> 0x00000118:  3c400000  lis      r2, 0
> 0x0000011c:  60428b00  ori      r2, r2, 0x8b00
> 0x00000120:  f821ff91  stdu     r1, -0x70(r1)
>
> Raise exception at 00000120 => 00000060 (21)
> invalid/unsupported opcode: 00 - 00 - 00 - 00 (00000000) fff00700 0
> ----------------
> IN:
> 0xfff00700:  00000000  .byte    0x00, 0x00, 0x00, 0x00
>
> Raise exception at fff00700 => 00000060 (21)
>
> The last part jumping to program exception vector is because we don't 
> have any handler installed at that address yet but the first exception 
> is the real problem which looks like vof has another opcode not 
> supported on a G4 CPU. Could it be compiled with some options to only 
> use PPC 32 opcodes or where does this stdu come from?

Agrh. It is "stdu" from pc-bios/vof/entry.S, looks like yet another bug 
since I enforce MSR to 32bit and whole firmware is 32bit too, I need to 
avoid those double word instructions. Also might need -mcpu=power4, 
juuuuuust in case.


--
Alexey