From: Segher Boessenkool <segher@kernel.crashing.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Christian Zigotzky <chzigotzky@xenosoft.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
kvm@vger.kernel.org,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
hypexed@yahoo.com.au, mad skateman <madskateman@gmail.com>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: KVM-PR no longer works when compiled with new GCC compilers
Date: Fri, 24 Apr 2026 21:50:44 -0500 [thread overview]
Message-ID: <aewsBF4zLRE7ZMuc@gate> (raw)
In-Reply-To: <d9ad0cd6fa640f23c396778bce2aa322e40e7e88.camel@physik.fu-berlin.de>
On Fri, Apr 24, 2026 at 05:48:37PM +0200, John Paul Adrian Glaubitz wrote:
> On Fri, 2026-04-24 at 16:47 +0200, Christian Zigotzky wrote:
> > I compiled it with "mtune=power4" today but without any success.
> >
> > Error messages:
> >
> > [ 800.274759] Couldn't emulate instruction 0x00000000 (op 0 xop 0)
> > [ 800.274767] kvmppc_exit_pr_progint: emulation at 100 failed (00000000)
>
> What exactly are you running inside the KVM? 0x00000000 doesn't seem like
> a valid instruction and a quick Google research reveals that this triggers
> a SIGLL trap.
By definition anything with primary op 0 (the first six bits 0) is
invalid. It isn't super unusual to (accidentally) try to execute a zero
as an instruction ;-)
Segher
prev parent reply other threads:[~2026-04-25 2:51 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
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 [this message]
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=aewsBF4zLRE7ZMuc@gate \
--to=segher@kernel.crashing.org \
--cc=chzigotzky@xenosoft.de \
--cc=debian-powerpc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.