From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH] sparc32 irq clearing (guest Solaris performance+NetBSD) fix
Date: Mon, 16 Nov 2009 23:44:07 +0100 [thread overview]
Message-ID: <fb8d4f70911161444s7e184012w970cc4f097b8b96@mail.gmail.com> (raw)
In-Reply-To: <20091116223521.GC12063@shareable.org>
2009/11/16 Jamie Lokier <jamie@shareable.org>:
> Artyom Tarasenko wrote:
>> I don't know, how the real sun4m reacts in the case where irq stays
>> on, not being cleared.
>> It can not be though that it would try to process irq for every next
>> tick. The CPU must have some time to clear the pending irq, so it must
>> be edge triggered too, at least in a way.
>
> In general, most CPUs have a "disable interrupts" flag which is set at
> the same time as calling the irq handler.
I see. The handler has enough time to clear pending irq then. Maybe
there is really no latch.
next prev parent reply other threads:[~2009-11-16 22:44 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
2009-11-16 22:50 ` Artyom Tarasenko
2009-11-16 22:35 ` Jamie Lokier
2009-11-16 22:44 ` Artyom Tarasenko [this message]
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=fb8d4f70911161444s7e184012w970cc4f097b8b96@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--cc=jamie@shareable.org \
--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).