9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] kenfs question?
Date: Sun,  7 Feb 2010 10:42:10 +0000	[thread overview]
Message-ID: <7d9191a1033cef725ecab7ffc88d1d01@terzarima.net> (raw)
In-Reply-To: <e75ecaade32da4958c9e9795f314ddeb@brasstown.quanstro.net>

> I guess I wasn't clear; what I was asking was why it was safe to
> attempt to take a lock when splhi() at all.

because such a lock is always taken with splhi, using ilock.
you might find in older code the use of lock in interrupt handlers,
protected by the implicit splhi of interrupt handling, and in
a few cases explicit splhi calls before lock.



  reply	other threads:[~2010-02-07 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06 16:12 Venkatesh Srinivas
2010-02-06 16:16 ` erik quanstrom
2010-02-11 13:31   ` Venkatesh Srinivas
2010-02-11 14:55     ` erik quanstrom
2010-02-07  0:12 ` Russ Cox
2010-02-07  3:02   ` Venkatesh Srinivas
2010-02-07  4:44     ` erik quanstrom
2010-02-07 10:42       ` Charles Forsyth [this message]
2010-02-07 12:19         ` Venkatesh Srinivas

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=7d9191a1033cef725ecab7ffc88d1d01@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).