From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx, kproc and *double sleep*
Date: Sat, 12 Jun 2010 23:15:31 +0100 [thread overview]
Message-ID: <64a6fa23d8a01d86312954ab451692d0@terzarima.net> (raw)
In-Reply-To: <AANLkTimFWKiVUowEyMOehT5r3fs--xdv25eS05g8zoG5@mail.gmail.com>
>in Linux parlance, Plan 9 is a "preemptible" kernel. Interrupt handlers can be interrupted, so to speak.
interrupt handlers are not normally interruptible during the interrupt
processing, but rather at the end (eg, when anyhigher, anyready or preempted
is called).
processes running at non-interrupt level in the kernel can be interrupted unless they are splhi
or using ilock.
>Except for the clock interrupt handler
that's only because the clock interrupt handler directly or indirectly (eg,
via sched) calls spllo, and other trap or interrupt handlers could do that.
next prev parent reply other threads:[~2010-06-12 22:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 14:06 Philippe Anel
2010-06-11 14:40 ` ron minnich
2010-06-11 14:49 ` erik quanstrom
2010-06-11 14:54 ` Philippe Anel
2010-06-11 15:03 ` erik quanstrom
2010-06-11 15:22 ` Philippe Anel
2010-06-11 15:25 ` Philippe Anel
2010-06-11 14:59 ` Philippe Anel
2010-06-11 17:11 ` Bakul Shah
2010-06-11 17:31 ` Philippe Anel
2010-06-11 18:34 ` Bakul Shah
2010-06-11 18:36 ` erik quanstrom
2010-06-11 18:51 ` Philippe Anel
2010-06-12 7:02 ` Philippe Anel
2010-06-12 9:22 ` Philippe Anel
2010-06-12 11:51 ` erik quanstrom
2010-06-13 13:01 ` Richard Miller
2010-06-13 13:43 ` Philippe Anel
2010-06-13 14:26 ` Philippe Anel
2010-06-13 16:20 ` ron minnich
2010-06-13 16:34 ` Philippe Anel
2010-06-13 17:23 ` Philippe Anel
2010-06-13 18:03 ` Philippe Anel
2010-06-14 19:15 ` Charles Forsyth
2010-06-14 19:36 ` Philippe Anel
2010-06-15 2:57 ` ron minnich
2010-06-15 3:36 ` ron minnich
2010-06-12 20:15 ` Richard Miller
2010-06-12 20:30 ` ron minnich
2010-06-12 22:15 ` Charles Forsyth [this message]
2010-06-13 0:04 ` ron minnich
2010-06-13 13:32 ` erik quanstrom
2010-06-13 22:34 ` Charles Forsyth
2010-06-13 9:00 ` Richard Miller
2010-06-11 14:49 ` Philippe Anel
2010-06-11 14:59 ` ron minnich
2010-06-11 15:02 ` ron minnich
2010-06-11 15:04 ` erik quanstrom
2010-06-11 15:43 ` ron minnich
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=64a6fa23d8a01d86312954ab451692d0@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@9fans.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).