public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Brice Goglin <brice@myri.com>
Cc: Matt Porter <mporter@embeddedalley.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] Simple userspace interface for PCI drivers
Date: Thu, 31 Aug 2006 21:27:50 -0700	[thread overview]
Message-ID: <20060901042750.GA2230@kroah.com> (raw)
In-Reply-To: <44F7AB16.30405@myri.com>

On Thu, Aug 31, 2006 at 11:37:58PM -0400, Brice Goglin wrote:
> Greg KH wrote:
> >> Additionally, the current code might not be flexible enough regarding
> >> acknowledging of interrupts. It might be good to use the bit that PCI
> >> 2.2 defines in the config space to mask/unmask interrupt in a generic
> >> way. Something like : when an interrupt comes, the driver mask the
> >> interrupts using this bit, and then passes the event to user-space. The
> >> user-space interrupt handler acknowledges the interrupt with the device
> >> specific code, and then unmask with the PCI 2.2 bit.
> >>     
> >
> > You can do that today with this code.  Remember, you have to have a
> > tiny kernelspace portion of your driver to handle the interrupt.  You
> > can do whatever you want in that interrupt handler.
> >   
> 
> The whole point of masking interrupt with this config-space bit is that
> we might not need any tiny kernelspace portion for our driver anymore.
> It won't work for devices that are not PCI 2.2 compliant. But, it might
> be good for the ones that are?

I don't really know.  I think 2.2 PCI devices might still be a bit rare,
but do not know for sure.

thanks,

greg k-h

  reply	other threads:[~2006-09-01  4:28 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  6:23 [RFC] Simple userspace interface for PCI drivers Greg KH
2006-08-30 10:09 ` Thomas Gleixner
2006-08-30 14:34 ` Matt Porter
2006-08-30 16:25   ` Thomas Gleixner
2006-08-30 17:55   ` Greg KH
2006-08-30 20:32     ` Foli Ayivoh
2006-08-30 21:01     ` Matthias Schniedermeyer
2006-08-30 21:25       ` linux-os (Dick Johnson)
2006-08-30 22:08         ` Greg KH
2006-09-01  1:36     ` Brice Goglin
2006-09-01  3:22       ` Greg KH
2006-09-01  3:37         ` Brice Goglin
2006-09-01  4:27           ` Greg KH [this message]
2006-08-31 13:49   ` Andi Kleen
2006-09-01 18:16     ` Greg KH
2006-08-30 17:07 ` Manu Abraham
2006-08-30 17:52   ` Greg KH
2006-08-30 22:50     ` Manu Abraham
2006-08-31  0:17       ` Greg KH
2006-08-31 13:24         ` Manu Abraham
2006-08-31 22:42           ` Greg KH
2006-08-31  7:40 ` Andrew Morton
2006-08-31  8:05   ` Thomas Gleixner
2006-08-31  8:30 ` Xavier Bestel
2006-08-31 20:39   ` Lee Revell
2006-08-31 20:53     ` Chris Friesen
2006-08-31 21:39       ` Greg KH
2006-08-31 20:58     ` Xavier Bestel
2006-08-31 21:12       ` Lee Revell
2006-08-31 21:18         ` Xavier Bestel
2006-08-31 21:33           ` Manu Abraham
2006-08-31 21:40       ` Greg KH
2006-09-01 21:17 ` Pavel Machek
2006-09-03  8:34   ` Thomas Gleixner
2006-09-12 19:47 ` Sam Ravnborg
2006-09-14  5:57   ` Greg KH

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=20060901042750.GA2230@kroah.com \
    --to=greg@kroah.com \
    --cc=brice@myri.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mporter@embeddedalley.com \
    --cc=tglx@linutronix.de \
    /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