linux-kernel - Re: [RFC] Simple userspace interface for PCI drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 31 Aug 2006 20:22:36 -0700
From:	Greg KH <greg@...ah.com>
To:	Brice Goglin <brice@...i.com>
Cc:	Matt Porter <mporter@...eddedalley.com>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC] Simple userspace interface for PCI drivers

On Thu, Aug 31, 2006 at 09:36:08PM -0400, Brice Goglin wrote:
> I might be nice to have something like a copy-block where the
> application writes/reads data, while the device does DMA only from/to
> there. We would need an easy way to mmap some anonymous DMA-ready memory
> in user-space, and something to give the corresponding DMA addresses to
> the application.

Sure, send a patch :)

> 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.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/