All of lore.kernel.org
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: matheus.ferst@eldorado.org.br,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Bug in qemu-system-ppc running fedora 12 ppc guest
Date: Thu, 29 Jul 2021 12:06:59 +0200 (CEST)	[thread overview]
Message-ID: <214af2d-c11e-862d-2c4c-4273ef4cef1b@eik.bme.hu> (raw)
In-Reply-To: <CABLmASFwffwhuNKTxfxUvHjCxZQHV+BiBTWeu0XoqRC0E1UU9A@mail.gmail.com>

Hello,

On Thu, 29 Jul 2021, Howard Spoelstra wrote:
> Hi,
>
> Qemu-system-ppc built from current master can no longer run Fedora 12 ppc
> as guest. (This the only ppc distro I tested.) Host is Fedora 34. Please
> see screen shot attached.
> Booting from both an installation DVD and from an installed system fail.
>
> To reproduce:
> compile qemu-system-ppc from current master and run:
>
> ./qemu-system-ppc \
> -M mac99,via=pmu \
> -m 1024 \
> -L pc-bios \
> -boot d \
> -cdrom Fedora-12-ppc-DVD.iso \
> -g 1024x768x8
>
> I tracked the issue down to this commit:
>
> 8f0a4b6a9b40e18116a2bb6bbcc00feb8119c792 is the first bad commit
> commit 8f0a4b6a9b40e18116a2bb6bbcc00feb8119c792

There's a fix for a similar problem I've seen with AROS and pegasos2 
firmware 1.2 that's in today's pull request:

https://lists.nongnu.org/archive/html/qemu-ppc/2021-07/msg00281.html

That should likely fixes this. Can you try with that (either once it's 
merged or from David's for-6.1 branch).

Regards,
BALATON Zoltan

> Author: Matheus Ferst <matheus.ferst@eldorado.org.br>
> Date:   Tue Jun 1 16:35:28 2021 -0300
>
>    target/ppc: Move cmp/cmpi/cmpl/cmpli to decodetree
>
>    Additionally, REQUIRE_64BIT when L=1 to match what is specified in The
>    Programming Environments Manual:
>
>    "For 32-bit implementations, the L field must be cleared, otherwise the
>    instruction form is invalid."
>
>    Some CPUs are known to deviate from this specification by ignoring the
>    L bit [1]. The stricter behavior, however, can help users that test
>    software with qemu, making it more likely to detect bugs that would
>    otherwise be silent.
>
>    If deemed necessary, a future patch can adapt this behavior based on
>    the specific CPU model.
>
>    [1] The 601 manual is the only one I've found that explicitly states
>    that the L bit is ignored, but we also observe this behavior in a 7447A
>    v1.2.
>
>    Signed-off-by: Matheus Ferst <matheus.ferst@eldorado.org.br>
>    Message-Id: <20210601193528.2533031-15-matheus.ferst@eldorado.org.br>
>    Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>    [dwg: Corrected whitespace error]
>    Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>
> target/ppc/insn32.decode                   | 14 ++++++++
> target/ppc/translate.c                     | 52
> ------------------------------
> target/ppc/translate/fixedpoint-impl.c.inc | 31 ++++++++++++++++++
> 3 files changed, 45 insertions(+), 52 deletions(-)
>
> Best,
> Howard
>
> [image: Qemu-system-ppc-Fedora-Crashing.png]
>


  reply	other threads:[~2021-07-29 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  7:55 Bug in qemu-system-ppc running fedora 12 ppc guest Howard Spoelstra
2021-07-29 10:06 ` BALATON Zoltan [this message]
2021-07-31  4:34   ` Howard Spoelstra

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=214af2d-c11e-862d-2c4c-4273ef4cef1b@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=hsp.cat7@gmail.com \
    --cc=matheus.ferst@eldorado.org.br \
    --cc=qemu-devel@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 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.