LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: BALATON Zoltan <balaton@eik.bme.hu>,
	Andrew Randrianasulu <randrianasulu@gmail.com>
Cc: qemu-ppc@nongnu.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Does kvm_pr work on G5 mac with host kernel 6.12.xx ?
Date: Mon, 15 Jun 2026 20:12:31 +0200	[thread overview]
Message-ID: <2d037b7b-6bdf-4aaa-9e2d-d26530d668d8@kernel.org> (raw)
In-Reply-To: <8f2fb26e-f406-261a-f9b7-8a1a032bf4df@eik.bme.hu>



Le 15/06/2026 à 15:33, BALATON Zoltan a écrit :
> On Mon, 15 Jun 2026, Andrew Randrianasulu wrote:
>> I also tried to see "info registers" as you showed in another email from
>> 2021 where you tried to use kvm-pr on qemu-emulated G5 and it showed
>>
>> info registers
>>                NIP 0000000000000700   LR 0000000000000000 CTR
>> 0000000000000000 XER 0000000000000000 CPU#0
>> MSR 8000000000000000 HID0 0000000060000000  HF 8000000000000000 iidx 3 
>> didx
>> 3                      TB 00000000 00000000 DECR 0
>>                                              GPR00 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> GPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>                        GPR08 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000                          GPR12
>> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> GPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>                        GPR20 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000                          GPR24
>> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>                  GPR28 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000
>> CR 00000000  [ -  -  -  -  -  -  -  -  ]             RES ffffffffffffffff
>>                        FPR00 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000                          FPR04
>> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>                  FPR08 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000
>> FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>                        FPR16 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000                          FPR20
>> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>                  FPR24 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000                          FPR28 0000000000000000
>> 0000000000000000 0000000000000000 0000000000000000
>> FPSCR 0000000000000000
>>                        SRR0 0000000000000100  SRR1 8000000000080000    
>> PVR
>> 00000000003c0301 VRSAVE 0000000000000000      SPRG0 0000000000000000 
>> SPRG1
>> 0000000000000000  SPRG2 0000000000000000  SPRG3 0000000000000000      
>> SPRG4
>> 0000000000000000 SPRG5 0000000000000000  SPRG6 0000000000000000  SPRG7
>> 0000000000000000
>> SDR1 0000000000000000   DAR 0000000000000000  DSISR 0000000000000000
>>
>> (qemu) q
>>
>> not sure if instruction pointer moved or not ...
>>
>> looking at some scroll buffer in Termux (I ssh into powermac ) it was at
>> 700 all 3 times I typed "info registers" into qemu monitor.
>>
>> but this debug msg
>>
>> [154992.595845] Couldn't emulate instruction 0x00000000 (op 0 xop 0)
>> [154992.595859] kvmppc_exit_pr_progint: emulation at 100 failed 
>> (00000000)
>>
>>
>> fills logs FAST!
> 
> NIP=0x700 is illegal instruction exception due to trying to execute 0 
> opcode at 0x100 which is the reset vector but shouldn't it try to start 
> at 0xfff00100? Maybe there's some issue with setting up KVM correctly?

On powerpc32 it is 0x100 or 0xfff00100 based on whether bit IP 
(Interrupt Prefix) is 0 or 1 in MSR register.

On powerpc64 MSR[IP] doesn't exist.

Christophe

> You can trace what is executed in TCG with -d in_asm but that does not 
> work for KVM as it's a TCG debug option. I don't know how to trace 
> execution with KVM but probably there are some trace points for that. 
> Maybe you get some info with -trace enable="kvm*" but I don't know how 
> to understand that output.
> 
> Regards,
> BALATON Zoltan
> 



  parent reply	other threads:[~2026-06-15 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+rFky7UDpHYFXvEiq91dpnfLuKCiaONctmW-q2jONmNG25Wow@mail.gmail.com>
     [not found] ` <418f045e-7aaf-c48b-4f08-018625b2c3e6@eik.bme.hu>
2026-06-14 19:03   ` Does kvm_pr work on G5 mac with host kernel 6.12.xx ? Andrew Randrianasulu
2026-06-14 20:35     ` BALATON Zoltan
2026-06-15  9:26       ` Andrew Randrianasulu
2026-06-15 13:33         ` BALATON Zoltan
2026-06-15 15:38           ` Andrew Randrianasulu
2026-06-15 18:12           ` Christophe Leroy (CS GROUP) [this message]
2026-06-15 18:54             ` BALATON Zoltan
2026-06-15 18:10         ` Christophe Leroy (CS GROUP)

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=2d037b7b-6bdf-4aaa-9e2d-d26530d668d8@kernel.org \
    --to=chleroy@kernel.org \
    --cc=balaton@eik.bme.hu \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=randrianasulu@gmail.com \
    /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