Messages in this thread | | | Date | Sat, 12 Mar 2005 21:03:39 -0500 | From | Jon Smirl <> | Subject | Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11) |
| |
On Fri, 11 Mar 2005 19:14:13 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote: > I posted a proposal for this sometime ago because X has some uses for > it. The idea being you'd pass a struct that describes > > 1. What tells you an IRQ occurred on this device > 2. How to clear it > 3. How to enable/disable it. > > Something like > > struct { > u8 type; /* 8, 16, 32 I/O or MMIO */ > u8 bar; /* PCI bar to use */ > u32 offset; /* Into bar */ > u32 mask; /* Bits to touch/compare */ > u32 value; /* Value to check against/set */ > } >
It might useful to add this to the main kernel API, and then over time modify all of the drivers to use it. If a driver does this it would be safe to transparently move it to user space like in UML or xen. I've been told that PCI Express and MSI does not have this problem.
-- Jon Smirl jonsmirl@gmail.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |