From: Albert Cahalan <albert@users.sf.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
peterc@gelato.unsw.edu.au
Subject: Re: User mode drivers: part 2: PCI device handling (patch 1/2 for 2.6.11)
Date: Fri, 11 Mar 2005 16:04:28 -0500 [thread overview]
Message-ID: <1110575069.1949.72.camel@cube> (raw)
In-Reply-To: <1110568542.15927.76.camel@localhost.localdomain>
On Fri, 2005-03-11 at 19:15 +0000, Alan Cox wrote:
> > You forgot the PCI domain (a.k.a. hose, phb...) number.
> > Also, you might encode bus,slot,function according to
> > the PCI spec. So that gives:
> >
> > long usr_pci_open(unsigned pcidomain, unsigned devspec, __u64 dmamask);
>
> Still insufficient because the device might be hotplugged on you. You
> need a file handle that has the expected revocation effects on unplug
> and refcounts
I was under the impression that a file handle would be returned.
I'm not so sure that is a sane way to handle hot-plug though.
First of all, in general, it's going to be like this:
Fan, meet shit.
Shit, meet fan.
Those who care might best be served by SIGBUS with si_code
and si_info set appropriately. Perhaps a revoke() syscall
that handled mmap() would work the same way.
next prev parent reply other threads:[~2005-03-11 21:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 5:18 User mode drivers: part 2: PCI device handling (patch 1/2 for 2.6.11) Albert Cahalan
2005-03-11 19:15 ` Alan Cox
2005-03-11 21:04 ` Albert Cahalan [this message]
2005-03-14 13:34 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 3:37 Peter Chubb
2005-03-11 7:18 ` Greg KH
2005-03-11 8:34 ` Peter Chubb
2005-03-11 10:31 ` Pavel Machek
2005-03-11 15:21 ` Greg KH
2005-03-11 16:45 ` Jesse Barnes
2005-03-12 22:43 ` Jon Smirl
2005-03-14 0:13 ` Peter Chubb
2005-03-14 17:46 ` Alan Cox
2005-03-11 19:16 ` Alan Cox
2005-03-12 10:49 ` Andrew Grover
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=1110575069.1949.72.camel@cube \
--to=albert@users.sf.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albert@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterc@gelato.unsw.edu.au \
/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