From: Jamie Lokier <jamie@shareable.org>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Artyom Tarasenko <atar4qemu@googlemail.com>
Subject: Re: [Qemu-devel] Re: [PATCH] sparc32 irq clearing (guest Solaris performance+NetBSD) fix
Date: Mon, 16 Nov 2009 22:31:21 +0000 [thread overview]
Message-ID: <20091116223121.GB12063@shareable.org> (raw)
In-Reply-To: <f43fc5580911161353r6051fdceg201fbf8499604339@mail.gmail.com>
Blue Swirl wrote:
> This patch makes the interrupts latch: ignore source clearing the
> interrupt. It seems be ~okay for my usual test setup, but does not
> help NetBSD 1.3.3. Some other NetBSD tests are changed, but they
> crashed before.
I'd expect the worst that would happen is "spurious interrupt"
messages under some kernel, according to the earlier description of
how Solaris handles interrupts (which is quite usual).
At least you'd expect the behaviour to be fine because no interrupts
are lost.
Drivers which go wrong because their interrupt handler is called
unnecessarily (or at least the "test device has condition pending"
function) tend to be rather fragile, because it's expected when
interrupt lines are shared between devices.
Then again, some old devices never did shared interrupt lines much.
-- Jamie
next prev parent reply other threads:[~2009-11-16 22:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 1:03 [Qemu-devel] [PATCH] sparc32 irq clearing (guest Solaris performance+NetBSD) fix Artyom Tarasenko
2009-11-14 15:26 ` [Qemu-devel] " Blue Swirl
2009-11-14 23:15 ` Artyom Tarasenko
2009-11-15 22:13 ` Blue Swirl
2009-11-16 11:47 ` Artyom Tarasenko
2009-11-16 16:14 ` Blue Swirl
2009-11-16 17:19 ` Artyom Tarasenko
2009-11-16 21:53 ` Blue Swirl
2009-11-16 22:31 ` Jamie Lokier [this message]
2009-11-16 22:50 ` Artyom Tarasenko
2009-11-16 22:35 ` Jamie Lokier
2009-11-16 22:44 ` Artyom Tarasenko
2009-11-17 20:45 ` Blue Swirl
2010-01-15 22:37 ` Artyom Tarasenko
2009-11-16 16:45 ` Artyom Tarasenko
2009-11-16 22:27 ` Jamie Lokier
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=20091116223121.GB12063@shareable.org \
--to=jamie@shareable.org \
--cc=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).