From: Blue Swirl <blauwirbel@gmail.com>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: qemu-devel@nongnu.org, Artyom Tarasenko <atar4qemu@gmail.com>
Subject: [Qemu-devel] Re: sparc32 do not clear interrupts when masking
Date: Sat, 16 Jan 2010 08:16:21 +0000 [thread overview]
Message-ID: <f43fc5581001160016n42a154bt510edf2747d88d95@mail.gmail.com> (raw)
In-Reply-To: <1263595050-17791-1-git-send-email-atar4qemu@google.com>
On Fri, Jan 15, 2010 at 10:37 PM, Artyom Tarasenko
<atar4qemu@googlemail.com> wrote:
> Don't clear interrupts on disabling, because
> * Sun4M_SystemArchitecture_edited2.pdf doesn't describe
> that masking or un-masking IRQ shall clear pending ones.
>
> * Field tests also show that SPARCstation-20 doesn't
> clear them.
Awesome work!
> * The patch makes Solaris 2.5.1/2.6 boot ~1500 times
> faster (~20 seconds instead of ~8 hours)
Unfortunately there is some problem with the patch (or more likely
there is some other bug that this uncovers), because all my Linux test
now panic. NetBSD and OpenBSD are unaffected.
For example, sparc-test:
eth0: LANCE 52:54:00:12:34:56
esp0: no command in esp_handle()
Kernel panic - not syncing: esp_handle: current_SC == penguin within interrupt!
<0>Press L1-A to return to the boot prom
The bug may be in ESP interrupt handling (or in the interrupt chain
between ESP, DMA controller and interrupt controller) as the panic
always happens in ESP probe.
next prev parent reply other threads:[~2010-01-16 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 22:37 [Qemu-devel] sparc32 do not clear interrupts when masking Artyom Tarasenko
2010-01-16 8:16 ` Blue Swirl [this message]
2010-01-16 8:47 ` [Qemu-devel] " Blue Swirl
2010-01-16 9:10 ` Blue Swirl
2010-01-16 9:31 ` Blue Swirl
2010-01-17 18:42 ` Artyom Tarasenko
2010-01-17 19:51 ` 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=f43fc5581001160016n42a154bt510edf2747d88d95@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=atar4qemu@gmail.com \
--cc=atar4qemu@googlemail.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).