From: Jeff Dike <jdike@karaya.com>
To: mingo@elte.hu
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Davide Libenzi <davidel@xmailserver.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: The O(1) scheduler breaks UML
Date: Mon, 14 Jan 2002 14:14:34 -0500 [thread overview]
Message-ID: <200201141914.OAA04168@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Mon, 14 Jan 2002 10:40:16 +0100." <Pine.LNX.4.33.0201140954300.2248-100000@localhost.localdomain>
mingo@elte.hu said:
> i'd suggest to find some other solution for UML, besides signals.
You suggest implementing interrupts with something other than signals? What
else is there?
In any case, I stuck a little kludge in _switch_to which checks for pending
SIGIO and, if there is one, hits the incoming process with a SIGIO. This
seems to do the trick.
Jeff
prev parent reply other threads:[~2002-01-14 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 2:39 The O(1) scheduler breaks UML Jeff Dike
2002-01-14 2:55 ` Davide Libenzi
2002-01-14 4:49 ` Jeff Dike
2002-01-14 9:55 ` Ingo Molnar
2002-01-14 15:38 ` Davide Libenzi
2002-01-14 9:40 ` Ingo Molnar
2002-01-14 19:14 ` Jeff Dike [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=200201141914.OAA04168@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.