Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11)

From: Jon Smirl (jonsmirl_at_gmail.com)
Date: 03/15/05

  • Next message: Jon Smirl: "Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11)"
    Date:	Mon, 14 Mar 2005 22:15:36 -0500
    To: Alan Cox <alan@lxorguk.ukuu.org.uk>
    
    

    On Mon, 14 Mar 2005 13:33:31 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
    > On Llu, 2005-03-14 at 00:02, Peter Chubb wrote:
    > > I can see there'd be problems if the code allowed shared interrupts,
    > > but it doesn't.
    >
    > If you don't allow shared IRQ's its useless, if you do allow shared
    > IRQ's it deadlocks. Take your pick 8)
    >
    > As to your comment about needing to do a few more I/O operations I
    > agree. However if your need is for speed then you might want to just
    > write a small IRQ helper module for the kernel or extend the syntax I
    > proposed a little (its conveniently trivial to generate native code from
    > this).

    The concept of passing in a little structure telling how to
    acknowledge an interrupt is a very good one. I'd like to see it added
    as a kernel feature so that drivers could start being converted to it.
    This is a big deal for Xen since Xen has the same problem with
    forwarded IRQs. Xen would pass the little structure from the domain to
    the supervisor so that the supervisor could cut off the IRQ if the
    domain fails.

    >
    > There isn't much you can do about the status read without MWI on most
    > chip designs (some get it right by posting status to system memory but
    > not many)
    >
    > Alan
    >
    > -
    > 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/
    >

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

  • Next message: Jon Smirl: "Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11)"

    Relevant Pages

    • Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
      ... I am planning to disable only leagacy shared interrupts (irq pin assertion/INTx ... > that you want to dump - ie get a consistent snapshot. ... Some other solution is needed for hardware predating PCI2.3. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11)
      ... On Llu, 2005-03-14 at 00:02, Peter Chubb wrote: ... > I can see there'd be problems if the code allowed shared interrupts, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: PATCH: 2.6.26-rc8: Fix IRQF_DISABLED for shared interrupts
      ... For shared interrupts IRQF_DISABLED will only take effect if the first ... For a shared IRQ, I would rather think that if any IRQ was flagged ... Seems like this patch ... I don't think you should need that flag; and if you did, ...
      (Linux-Kernel)
    • Re: [PATCH] uio: User IRQ Mode
      ... This patch adds a "User IRQ Mode" to UIO. ... This doesn't work even for some non shared interrupts. ... Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany ...
      (Linux-Kernel)
    • Re: [PATCH] kdump documentation update to introduce use of irqpoll
      ... >> helps in reducing driver initialization failures in second kernel due ... >> to shared interrupts. ... > Well that rather assumes we've merged the irqpoll patch. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)