From: Pavel Machek <pavel@ucw.cz>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11)
Date: Fri, 11 Mar 2005 11:29:20 +0100 [thread overview]
Message-ID: <20050311102920.GB30252@elf.ucw.cz> (raw)
In-Reply-To: <16945.4650.250558.707666@berry.gelato.unsw.EDU.AU>
Hi!
> As many of you will be aware, we've been working on infrastructure for
> user-mode PCI and other drivers. The first step is to be able to
> handle interrupts from user space. Subsequent patches add
> infrastructure for setting up DMA for PCI devices.
>
> The user-level interrupt code doesn't depend on the other patches, and
> is probably the most mature of this patchset.
Okay, I like it; it means way easier PCI driver development.
But... how do you handle shared PCI interrupts?
> This patch adds a new file to /proc/irq/<nnn>/ called irq. Suitably
> privileged processes can open this file. Reading the file returns the
> number of interrupts (if any) that have occurred since the last read.
> If the file is opened in blocking mode, reading it blocks until
> an interrupt occurs. poll(2) and select(2) work as one would expect, to
> allow interrupts to be one of many events to wait for.
> (If you didn't like the file, one could have a special system call to
> return the file descriptor).
This should go into Documentation/ somewhere.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-03-11 10:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 3:36 Peter Chubb
2005-03-11 10:29 ` Pavel Machek [this message]
2005-03-12 16:27 ` Jon Smirl
2005-03-12 18:55 ` Jon Smirl
2005-03-14 0:39 ` Peter Chubb
2005-03-14 1:24 ` Jon Smirl
2005-03-11 13:50 ` Michael Raymond
2005-03-11 17:25 ` Greg KH
2005-03-11 17:31 ` Michael Raymond
2005-03-11 19:14 ` Alan Cox
2005-03-13 2:03 ` Jon Smirl
2005-03-15 4:32 ` Lee Revell
2005-03-15 13:28 ` Alan Cox
2005-03-14 0:02 ` Peter Chubb
2005-03-14 13:33 ` Alan Cox
2005-03-15 3:15 ` Jon Smirl
2005-03-12 15:55 ` Jon Smirl
2005-03-12 17:11 ` Zwane Mwaikambo
2005-03-14 1:55 ` Jon Smirl
2005-03-14 3:04 ` Peter Chubb
2005-03-14 0:36 ` Peter Chubb
[not found] ` <9e47339105031317193c28cbcf@mail.gmail.com>
2005-03-14 1:42 ` Peter Chubb
2005-03-14 1:52 ` Jon Smirl
2005-03-14 3:06 ` Peter Chubb
2005-03-15 3:19 ` Jon Smirl
2005-03-15 3:47 ` Peter Chubb
2005-03-15 3:50 ` Jon Smirl
2005-03-15 4:11 ` Peter Chubb
2005-03-15 19:20 Stephen Warren
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=20050311102920.GB30252@elf.ucw.cz \
--to=pavel@ucw.cz \
--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
all inboxes | Powered by JetHome®