public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	kvm@vger.kernel.org,
	"debian-powerpc@lists.debian.org"
	<debian-powerpc@lists.debian.org>
Cc: "R.T.Dickinson" <rtd2@xtra.co.nz>,
	hypexed@yahoo.com.au, mad skateman <madskateman@gmail.com>,
	Christian Zigotzky <info@xenosoft.de>
Subject: KVM-PR no longer works when compiled with new GCC compilers
Date: Thu, 23 Apr 2026 18:50:37 +0200	[thread overview]
Message-ID: <588ada6c-bcc4-e93b-1beb-4f7f859e3d5c@xenosoft.de> (raw)
In-Reply-To: <cfd779d6-9440-46b2-9ed5-752f1ae6b5d1@xenosoft.de>

On 02/10/25 08:37, Christian Zigotzky wrote:
> Hello,
>
> KVM-PR (-enable-kvm) doesn't work anymore on our PA Semi Nemo boards 
> [1] if we compiled it with new GCC compilers.
> The VM can't boot. There aren't any messages on the serial console of 
> QEMU.
>
> It boots without KVM-PR.
>
> Kernel config with new GCC compiler [2]:
>
> - CONFIG_CC_VERSION_TEXT="powerpc64-suse-linux-gcc (SUSE Linux) 11.5.0"
> - CONFIG_TARGET_CPU="power4"
> - CONFIG_TUNE_CPU="-mtune=power10"
>
> It works if I compile it with an old GCC compiler [3]:
>
> - CONFIG_CC_VERSION_TEXT="powerpc-linux-gnu-gcc (Ubuntu 
> 9.4.0-1ubuntu1~20.04.1) 9.4.0"
> - CONFIG_TARGET_CPU="power4"
> - CONFIG_TUNE_CPU="-mtune=power9"
>
> Mtune changes to power9 automatically if I compiled it with an old GCC 
> compiler. If I compile it with a new GCC compiler again it changes 
> automatically to mtune=power10.
>
> Is mtune the reason of the KVM-PR issue? I think the issue is the new 
> GCC. [4]
>
> Could you please check whether KVM-PR is compatible with new versions 
> of GCC compilers?
>
> Thanks in advance,
>
> Christian
>
>
>
> [1] https://en.wikipedia.org/wiki/AmigaOne_X1000
>
> [2] 
> https://github.com/chzigotzky/kernels/blob/45186997e6f347fd092f9ab629d62d6041426227/configs/x1000_defconfig
>
> [3] 
> https://github.com/chzigotzky/kernels/blob/bc7a3e27b3fcdee52a8135435f02cf807a43872a/configs/x1000_defconfig
>
> [4] KVM-PR no longer works on an X1000 if the kernel has been compiled 
> with a new GCC: 
> https://forum.hyperion-entertainment.com/viewtopic.php?p=57146#p57146
>
Error messages (kvm-pr compiled with powerpc64-linux-gnu-gcc 14.1.1 
20240507 Red Hat Cross 14.1.1-1, GNU ld version 2.41-2.el10_0):

[  800.274759] Couldn't emulate instruction 0x00000000 (op 0 xop 0)
[  800.274767] kvmppc_exit_pr_progint: emulation at 100 failed (00000000)

-- 
Sent with BrassMonkey 34.1.0 (https://github.com/chzigotzky/Web-Browsers-and-Suites-for-Linux-PPC/releases/tag/BrassMonkey_34.1.0)



  parent reply	other threads:[~2026-04-23 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  6:37 KVM-PR no longer works when compiled with new GCC compilers Christian Zigotzky
2025-10-02  6:52 ` Christophe Leroy
2026-04-23 16:50 ` Christian Zigotzky [this message]
2026-04-23 17:35   ` John Paul Adrian Glaubitz
2026-04-23 17:46     ` Christian Zigotzky
2026-04-24 14:47       ` Christian Zigotzky
2026-04-24 15:48         ` John Paul Adrian Glaubitz
2026-04-25  2:50           ` Segher Boessenkool

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=588ada6c-bcc4-e93b-1beb-4f7f859e3d5c@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=debian-powerpc@lists.debian.org \
    --cc=hypexed@yahoo.com.au \
    --cc=info@xenosoft.de \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=rtd2@xtra.co.nz \
    /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