From: helbig@Informatik.BA-Stuttgart.DE (Wolfgang Helbig)
Subject: [TUHS] re: Raise of interrupt level necessary
Date: Sun, 15 Dec 2002 10:52:22 +0100 (MET) [thread overview]
Message-ID: <200212151154.gBFBsdb02344@bsd.korb> (raw)
>Date: Sat, 14 Dec 2002 15:27:40 -0800
Michael Davidson wrote:
>If you think that the "rule" is "no ISR can touch user space while
>interrupting a kernel process", then it is display() that breaks
>the rule.
The point is, that this rule leads to somewhat simpler and therefore
better code -- breaking the rule calls for some justification.
Calling display() from the clock-ISR is the only place where an ISR does
not conform to this rule.
Greetings
Wolfgang Helbig
next reply other threads:[~2002-12-15 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 9:52 Wolfgang Helbig [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-16 21:43 Ian King
2002-12-14 8:47 Wolfgang Helbig
2002-12-14 23:27 ` Michael Davidson
2002-12-13 6:04 Dennis Ritchie
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=200212151154.gBFBsdb02344@bsd.korb \
--to=helbig@informatik.ba-stuttgart.de \
/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).