All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: u-boot@lists.denx.de
Cc: Andrew Jones <ajones@ventanamicro.com>
Subject: RISC-V u-boot unable to boot QEMU using '-cpu max'
Date: Mon, 22 Apr 2024 16:43:59 -0300	[thread overview]
Message-ID: <bed7e137-4613-4153-babc-3b8b7c911151@ventanamicro.com> (raw)

Hi,

In QEMU we have a 'max' type CPU that implements (almost) all extensions that QEMU
is able to emulate. Recently, in QEMU commit 249e0905d05, we bumped the extensions
for this CPU.

And after this commit this CPU is now unable to boot a guest using upstream
u-boot. Here's the error being thrown:

qemu-system-riscv64 \
         -machine virt -nographic -m 8G -smp 8 \
         -cpu max -kernel uboot.elf (...)
(...)

initcall sequence 000000008027c3e8 failed at call 000000008021259e (err=-28)
### ERROR ### Please RESET the board ###


I can get the guest to boot if I disable the following extensions from the 'max' CPU:

  -cpu max,zfbfmin=false,zvfbfmin=false,zvfbfwma=false

Due to QEMU extension dependencies I'm not able to disable these individually. What I can
say is that u-boot isn't playing ball to at least one of them.

Is this an u-boot bug? Up to this point I was assuming that u-boot would silently ignore
hart extensions that it doesn't support.


Thanks,


Daniel

             reply	other threads:[~2024-04-22 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 19:43 Daniel Henrique Barboza [this message]
2024-04-23  5:34 ` RISC-V u-boot unable to boot QEMU using '-cpu max' Leo Liang
2024-04-23 12:41   ` Conor Dooley
2024-04-23 12:52     ` Daniel Henrique Barboza
2024-04-23 14:23       ` Conor Dooley

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=bed7e137-4613-4153-babc-3b8b7c911151@ventanamicro.com \
    --to=dbarboza@ventanamicro.com \
    --cc=ajones@ventanamicro.com \
    --cc=u-boot@lists.denx.de \
    /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.