From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Greg Kurz <groug@kaod.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH qemu v19] spapr: Implement Open Firmware client interface
Date: Tue, 18 May 2021 15:13:29 +1000 [thread overview]
Message-ID: <3e3ebf5b-0adc-974e-4a3c-3c76bcc2ce37@ozlabs.ru> (raw)
In-Reply-To: <f9a45179-4c72-66eb-90f8-689e3969f4@eik.bme.hu>
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
next prev parent reply other threads:[~2021-05-18 5:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 12:58 [PATCH qemu v19] spapr: Implement Open Firmware client interface Alexey Kardashevskiy
2021-05-12 4:50 ` Alexey Kardashevskiy
2021-05-15 15:04 ` BALATON Zoltan
2021-05-15 19:31 ` BALATON Zoltan
2021-05-16 23:34 ` BALATON Zoltan
2021-05-17 4:27 ` Alexey Kardashevskiy
2021-05-17 13:45 ` BALATON Zoltan
2021-05-17 18:44 ` BALATON Zoltan
2021-05-18 5:13 ` Alexey Kardashevskiy [this message]
2021-05-17 4:15 ` Alexey Kardashevskiy
2021-05-17 12:17 ` BALATON Zoltan
2021-05-18 4:51 ` Alexey Kardashevskiy
2021-05-24 4:42 ` David Gibson
2021-05-24 11:50 ` BALATON Zoltan
2021-05-15 20:19 ` BALATON Zoltan
2021-05-17 3:24 ` Alexey Kardashevskiy
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=3e3ebf5b-0adc-974e-4a3c-3c76bcc2ce37@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--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).