From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [BUG] QEMU crash during cpu reset (MIPS regression)
Date: Fri, 4 May 2007 23:27:33 +0300 [thread overview]
Message-ID: <f43fc5580705041327q4dbb3d06r8da1d958d2eae2dc@mail.gmail.com> (raw)
In-Reply-To: <463B939A.1090508@mail.berlios.de>
On 5/4/07, Stefan Weil <weil@mail.berlios.de> wrote:
> Resetting a MIPS cpu currently does not work, because important
> entries in env (CPUMIPSState) are filled with 0 at the
> beginning of function cpu_reset.
>
> At system start, these values are set in cpu_mips_register.
>
> After reset, env->nb_tlb == 0 results in a division by zero
> crash of QEMU.
>
> We can either re-arrange the entries in CPUMIPSState
> (move those which must not be zero'ed to the end), or
> cpu_reset must call cpu_mips_register.
>
> Which solution is better?
I solved the same issue on Sparc side by not zeroing most of the
state. This is in line with the real Sparc hardware.
prev parent reply other threads:[~2007-05-04 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 20:12 [Qemu-devel] [BUG] QEMU crash during cpu reset (MIPS regression) Stefan Weil
2007-05-04 20:27 ` Paul Brook
2007-05-04 20:44 ` Stefan Weil
2007-05-04 20:27 ` Blue Swirl [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=f43fc5580705041327q4dbb3d06r8da1d958d2eae2dc@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).