From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 9/11] UML - Implement soft interrupts
Date: Tue, 17 Jan 2006 01:24:31 +0100 [thread overview]
Message-ID: <200601170124.32076.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200601152139.k0FLdp1G027747@ccure.user-mode-linux.org>
On Sunday 15 January 2006 22:39, Jeff Dike wrote:
> This patch implements soft interrupts. Interrupt enabling and
> disabling no longer map to sigprocmask. Rather, a flag is set
> indicating whether interrupts may be handled. If a signal comes in
> and interrupts are marked as OK, then it is handled normally. If
> interrupts are marked as off, then the signal handler simply returns
> after noting that a signal needs handling. When interrupts are enabled
> later on, this pending signals flag is checked, and the IRQ handlers
> are called at that point.
~25 %? Good! Which is delay vs. host?
A curiosity - did you look at the similar code in Ingo Molnar's VCPU patch? I
never found the time to split it out and compare differencies. I just
remember it using assembler inserts for (maybe atomic) bitmask manipulations.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
next prev parent reply other threads:[~2006-01-17 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 21:39 [PATCH 9/11] UML - Implement soft interrupts Jeff Dike
2006-01-17 0:24 ` Blaisorblade [this message]
2006-01-17 3:32 ` [uml-devel] " Jeff Dike
2006-01-17 14:17 ` Blaisorblade
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=200601170124.32076.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).