mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Stelian Pop <stelian.pop@fr.alcove.com>, linux-kernel@vger.kernel.org
Subject: Re: PCI driver in userspace
Date: Tue, 26 Feb 2002 17:59:03 -0700	[thread overview]
Message-ID: <200202270059.g1R0x3132421@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <200202270052.g1R0qdK11879@devserv.devel.redhat.com>
In-Reply-To: <D8E12241B029D411A3A300805FE6A2B9025761AB@montreal.eicon.com> <mailman.1014747181.29305.linux-kernel2news@redhat.com> <200202270052.g1R0qdK11879@devserv.devel.redhat.com>

Pete Zaitcev writes:
> >> I think this is a good example to start with. It has all the
> >> interresting features. I hope it also has interrupt handling
> >> to userspace (by generating SIGIO's). 
> > 
> > It hasn't, it just continually polls the I/O ports for 
> > completition.
> > 
> >> Although I dont know if this is a good idea in the first place.
> > 
> > I think it depends on the interrupt frequency, and other things.
> > 
> > Stelian.
> 
> PCI interrupts must be deactivated in the device before an
> interrupt driver returns and unmasks interrupt in the CPU.
> User processes run with interrupts open. This is why purely
> user level interrupts are IMPOSSIBLE (regardless of interrupt
> frequency).
> 
> Two natural ways to work around this problem are:
> 
> 1. Run user processes with interrupts closed (or at least one
> interrupt source disabled, if your architecture allows that).
> This is what RTOSes often do. I do not think it can be easily
> done on generic Linux.
> 
> 2. Write a small driver that deactivates interrupts and queues
> interrupt events (with SIGIO and some other means). Personally,
> I think that it is dumb in most cases, because once you wrote
> that driver stub, it takes very little work to move the rest
> of the driver into the kernel. The notable exception is XFree86,
> of course.
> 
> We must ask someone to add this to FAQ on tux.org.

Send me a patch to the HTML file.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2002-02-27  0:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1014747181.29305.linux-kernel2news@redhat.com>
2002-02-26 17:42 ` Daniel Shane
2002-02-26 18:10   ` Stelian Pop
2002-02-27  0:52   ` Pete Zaitcev
2002-02-27  8:26     ` Stelian Pop
2002-02-27  0:59 ` Richard Gooch [this message]
2002-02-26 14:55 Daniel Shane
2002-02-26 15:07 ` Martin Dalecki
2002-02-26 15:12 ` Stelian Pop

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=200202270059.g1R0x3132421@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian.pop@fr.alcove.com \
    --cc=zaitcev@redhat.com \
    /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®