All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Francis <1915027@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1915027] Re: RISC-V 64, CPUs do ilegal 0x00 write with SMP
Date: Tue, 23 Mar 2021 22:02:14 -0000	[thread overview]
Message-ID: <161653693429.20106.15224677154013166487.malone@wampee.canonical.com> (raw)
In-Reply-To: 161279694044.12775.4779161531525908683.malonedeb@soybean.canonical.com

Even with -smp 1 you will see the same errors. The problem is because
there is nothing to run after OpenSBI jumps to the next stage.

If you load a kernel you will not see the error messages.

** Changed in: qemu
       Status: New => Invalid

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1915027

Title:
  RISC-V 64, CPUs do ilegal 0x00 write with SMP

Status in QEMU:
  Invalid

Bug description:
  When QEMU is runt like this:

  qemu-system-riscv64 -d unimp,guest_errors -smp 8

  Other harts will do a illegal write on address 0x00.

  This could be mostly (i think) because the initial assembly code is
  only loaded on the first hart and the others do a mess because there
  is no code to execute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1915027/+subscriptions


      reply	other threads:[~2021-03-23 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 15:09 [Bug 1915027] [NEW] RISC-V 64, CPUs do ilegal 0x00 write with SMP superleaf1995
2021-03-23 22:02 ` Alistair Francis [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=161653693429.20106.15224677154013166487.malone@wampee.canonical.com \
    --to=1915027@bugs.launchpad.net \
    --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.