[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Is there way to log SPRs accessed by guest ?
|
From: |
Andrew Randrianasulu |
|
Subject: |
Re: Is there way to log SPRs accessed by guest ? |
|
Date: |
Wed, 12 Mar 2025 16:22:42 +0300 |
On Wed, Mar 12, 2025 at 3:58 PM BALATON Zoltan <balaton@eik.bme.hu> wrote:
>
> On Wed, 12 Mar 2025, Andrew Randrianasulu wrote:
> > I was taking detour into why macos X does not boot on -cpu 970 and found
> > this email exchange from 2018
> >
> > https://mail.coreboot.org/hyperkitty/list/openbios@openbios.org/thread/JEQTQ7BQLTFORWWKBLG6AOC5LRRTDVSD/
> >
> > I can see
> >
> > ====
> >
> > Trying to write invalid spr 276 (0x114) at 00000000000afc14
> > Trying to read invalid spr 277 (0x115) at 00000000000afc18
> > Trying to read invalid spr 276 (0x114) at 00000000000afc1c
> > Trying to write invalid spr 277 (0x115) at 00000000000afc38
> > Trying to write invalid spr 276 (0x114) at 00000000000afc3c
> > Trying to read invalid spr 276 (0x114) at 00000000000afc40
> > Trying to write invalid spr 277 (0x115) at 00000000000afcec
> > Trying to write invalid spr 276 (0x114) at 00000000000afcf0
> > Trying to read invalid spr 276 (0x114) at 00000000000afcf4
> > Trying to write invalid spr 304 (0x130) at 0000000000003d28
> > Trying to read invalid spr 304 (0x130) at 0000000000003d4c
> > Trying to write invalid spr 304 (0x130) at 0000000000003d28
> > Trying to read invalid spr 304 (0x130) at 0000000000003d4c
> > Trying to write invalid spr 304 (0x130) at 0000000000003d28
> > Trying to read invalid spr 304 (0x130) at 0000000000003d4c
> > Trying to write invalid spr 304 (0x130) at 0000000000003d28
> > Trying to read invalid spr 304 (0x130) at 0000000000003d4c
> > Trying to write invalid spr 304 (0x130) at 0000000000003d28
> > Trying to read invalid spr 304 (0x130) at 0000000000003d4c
> > Trying to write invalid spr 304 (0x130) at 0000000000003d28
> > Trying to read invalid spr 304 (0x130) at 0000000000003d4c
> >
> >
> > so it sort of stuck trying to do something with SPR 304 (some kind of
> > hypervisor register)
> >
> > But I can't repeat this experiment with my normal Tiger install, there is
> > no detailed info, just early hang on 970FX :(
> >
> >
> > Is there way to add printing SPR access to qemu?
>
> $ cd target/ppc
> $ git grep -n "invalid spr"
> translate.c:4124: "Trying to read invalid spr %d
> (0x%03x) at "
> translate.c:4302: "Trying to write invalid spr %d
> (0x%03x) at "
> $ view translate.c
> :4124
> /* Not defined */
> qemu_log_mask(LOG_GUEST_ERROR,
> "Trying to read invalid spr %d (0x%03x) at "
> TARGET_FMT_lx "\n", sprn, sprn, ctx->cia);
>
> so try -d guest_errors (and use above way to get around qemu sources and
> find things).
Thanks a lot, I usually do grep in *my* sources, qemu a bit
intimidating it seems ...
I tried OS 9.2 with usb-audio and ... it failed - after few seconds of
audio desktop disappear :)
./qemu-system-ppc -M mac99 -display sdl -hda ~/AndrewR/disk.qcow2 -
m 512 -device usb-audio -d guest_errors
cpus[0] = 0x77d16fc1d000 0x77d16fc1fb80
Trying to write invalid spr 0 (0x000) at 00f113c0
Trying to read invalid spr 0 (0x000) at 00f113c8
Trying to write privileged spr 955 (0x3bb) at 00f168c8
Trying to write invalid spr 959 (0x3bf) at 00f16930
Trying to read invalid spr 959 (0x3bf) at 00f16938
Trying to write privileged spr 955 (0x3bb) at 00f168c8
Trying to write invalid spr 959 (0x3bf) at 00f16930
Trying to read invalid spr 959 (0x3bf) at 00f16938
CUDA: unknown command 0x02
CUDA: unknown command 0x08
CUDA: unknown command 0x02
CUDA: unknown command 0x02
CUDA: unknown command 0x22
CUDA: unknown command 0x22
CUDA: unknown command 0x22
CUDA: unknown command 0x22
CUDA: unknown command 0x22
CUDA: unknown command 0x22
CUDA: unknown command 0x25
CUDA: unknown command 0x22
CUDA: unknown command 0x22
CUDA: unknown command 0x25
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
dbdma_unassigned_flush: use of unassigned channel 12
dbdma_unassigned_flush: use of unassigned channel 12
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 12
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 12
dbdma_unassigned_flush: use of unassigned channel 12
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 14
dbdma_unassigned_rw: use of unassigned channel 14
dbdma_unassigned_flush: use of unassigned channel 12
dbdma_unassigned_flush: use of unassigned channel 14
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x0b
CUDA: unknown command 0x24
CUDA: unknown command 0x0b
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
CUDA: unknown command 0x24
netbsd10$
But with osx 10.4.11 I saw no -d guest_errors with -cpu 970 ....
Do not worry too hard about this, I just play around (publically)
>
> Regards,
> BALATON Zoltan