9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Lyndon Nerenberg (VE6BBM/VE7TFX)"  <lyndon@orthanc.ca>
To: 9fans@9fans.net
Subject: [9fans] DMEXCL vs. QTEXCL
Date: Tue, 28 Dec 2010 15:27:19 -0800	[thread overview]
Message-ID: <1d28fe815c8b1c4dba7e9402c94a61f9@gandalf.orthanc.ca> (raw)

Given the overlap between (DM|QT)EXCL, it's not clear to me which
of these is considered the authority for indicating exclusive access.

devusb.c plays with DMEXCL, devcons.c with QTEXCL.  I'm assumed the
DMEXCL bit was magically getting propagated down to QTEXCL in
qid.type, but I'll be damned if I can find anything in the kernel that
actually does anything with either of these bits.  WTF am I missing?
This should be stunningly obvious.  Someone please stun me more than I
am :-P

My interest is in the context of `Chan's.

--lyndon




             reply	other threads:[~2010-12-28 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 23:27 Lyndon Nerenberg (VE6BBM/VE7TFX) [this message]
2010-12-29 14:30 ` C H Forsyth

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=1d28fe815c8b1c4dba7e9402c94a61f9@gandalf.orthanc.ca \
    --to=lyndon@orthanc.ca \
    --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).