[lkml]   [2005]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [Fastboot] Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
    Grant Grundler <> writes:

    > On Tue, Jun 07, 2005 at 03:59:18AM -0600, Eric W. Biederman wrote:
    > > > *lots* of PCI devices predate PCI2.3. Possibly even the majority.
    > >
    > > In general generic hardware bits for disabling DMA, disabling interrupts
    > > and the like are all advisory. With the current architecture things
    > > will work properly even if you don't manage to disable DMA (assuming
    > > you don't reassign IOMMU entries at least).
    > ISTR, pSeries (IBM), some alpha, some sparc64, and parisc (64-bit) require
    > use of the IOMMU for *any* DMA. ie IOMMU entries need to be programmed.
    > Probably want to make a choice to ignore those arches for now
    > or sort out how to deal with an IOMMU.

    The howto deal with an IOMMU has been sorted out but so far no one
    has actually done it. What has been discussed previously is simply
    reserving a handful of IOMMU entries, and then only using those
    in the crash recover kernel. This is essentially what we do with DMA
    on architectures that don't have an IOMMU and it seems quite safe
    enough there.

    > > Shared interrupts are an interesting case. The simplest solution I can
    > > think of for a crash dump capture kernel is to periodically poll
    > > the hardware, as if all interrupts are shared. At that level
    > > I think we could get away with ignoring all hardware interrupt sources.
    > Yes, that's perfectly ok. We are no longer in a multitasking env.

    Well we are at least capable of multitasking but that is no longer the
    primary focus. Having polling as at least an option should make
    debugging easier. Last I looked Andrews kernel hand an irqpoll option
    to do something very like this.

    > > Does anyone know of a anything that would break by always polling
    > > the hardware? I guess there could be a problem with drivers
    > > that don't understand shared interrupts, are there enough of those
    > > to be an issue.
    > PCI requires drivers support Shared IRQs.
    > A few oddballs might be broken but I expect networking/mass storage
    > drivers get this right.

    Agreed. Which means any drivers we really need for dumping the system
    should be fine. If the drivers don't work in that mode at least the
    concept of fixing it won't be controversial.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-06-07 20:53    [W:0.022 / U:3.592 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site