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 for Android: free password hash cracker in your pocket

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

Message-ID: <44F7AB16.30405@myri.com>
Date:	Thu, 31 Aug 2006 23:37:58 -0400
From:	Brice Goglin <brice@...i.com>
To:	Greg KH <greg@...ah.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

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?

Brice

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