From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [BUG] QEMU crash during cpu reset (MIPS regression)
Date: Fri, 04 May 2007 22:44:44 +0200 [thread overview]
Message-ID: <463B9B3C.8050103@mail.berlios.de> (raw)
In-Reply-To: <200705042127.21769.paul@codesourcery.com>
Paul Brook schrieb:
>> 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?
>
> ARM uses the latter solution.
> IMHO it's better to do that than try and extend the hacks were some
> fields are
> left untouched by a reset.
>
> Paul
>
I had just implemented this 2nd solution. It was not sufficient
because env->irq was also zero'ed, so Linux starts after
reset without the MIPS timer interrupt which is not good :-).
Re-arranging env->irq is not a nice solution but it helped.
Stefan
next prev parent reply other threads:[~2007-05-04 20:51 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 [this message]
2007-05-04 20:27 ` Blue Swirl
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=463B9B3C.8050103@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).