From: Jeff Dike <jdike@karaya.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: The O(1) scheduler breaks UML
Date: Sun, 13 Jan 2002 21:39:45 -0500 [thread overview]
Message-ID: <200201140239.VAA05307@ccure.karaya.com> (raw)
The new scheduler holds IRQs off across the call to context_switch. UML's
_switch_to expects them to be enabled when it is called, and things go
badly wrong when they are not.
Because UML has a host process for each UML thread, SIGIO needs to be
forwarded from one process to the next during a context switch. A SIGIO
arriving during the window between the disabling of IRQs and forwarding of
IRQs to the next process will be trapped on the process going out of
context. This happens fairly regularly and causes hangs because some process
is waiting for disk IO which never arrives because the process that was notified
of the completion is switched out.
So, is it possible to enable IRQs across the call to _switch_to?
Jeff
next reply other threads:[~2002-01-14 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 2:39 Jeff Dike [this message]
2002-01-14 2:55 ` The O(1) scheduler breaks UML 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
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=200201140239.VAA05307@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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