From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] sparc32 reset's regression
Date: Thu, 6 Aug 2009 11:26:59 +0200 [thread overview]
Message-ID: <fb8d4f70908060226m605b6274xe844aeb3a7370ad@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580908051133u7ca4ffdfh775db0ce05bf5e7c@mail.gmail.com>
> The commit looks fine to me. Would this patch happen to fix the bug?
Yes, this patch fixes the bug, thanks.
It can be though that the bug is not directly related to the initial commit.
There seems to be a race condition. Sometimes the bug didn't appear
even without the fix if I put a lot of DPRINTFs in irq handling in
sun4m.c and cpu-exec.c and turn the logging on. Unfortunately it's not
always reproducible, so I can't tell yet which printf hides the
problem.
prev parent reply other threads:[~2009-08-06 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 8:44 [Qemu-devel] sparc32 reset's regression Artyom Tarasenko
2009-08-05 18:33 ` Blue Swirl
2009-08-06 9:26 ` Artyom Tarasenko [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=fb8d4f70908060226m605b6274xe844aeb3a7370ad@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=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).