May 14, 2013
3:13 p.m.
On Tue, May 14, 2013 at 11:54 AM, Gergely Buday <gbuday@gmail.com> wrote:
Prabhu nath wrote:
But if the device has to generate an interrupt on the reception of the data then it is best for the driver code to be in the kernel space waiting for the data, rather than in the user space because there is no efficient mechanism till now for the control to be transferred to the waiting user space code on the reception of the interrupt.
What are the curently available mechanisms for an interrupt to propagate into user space?
See VFIO and UIO. Even the gpio sysfs interface allows you to catch interrupts.
Is there one that affects the scheduler?
??? -- Thanks, //richard