lkml.org 
[lkml]   [2004]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC/PATCH, 2/4] readX_check() performance evaluation
    On Wed, 28 Jan 2004 18:20:03 +0000
    Matthew Wilcox <willy@debian.org> wrote:


    > If there are, Linus' interface is probably the best one. If not, we could
    > simply have readX_check() / writeX_check() call dev->driver->unregister()
    > if they notice an error has occurred and then the driver doesn't even
    > need to call read_pcix_errors().

    It just won't really work for platforms with inexact MCEs for IO errors.
    And even for those with exact MCEs it would probably be a nightmare
    to implement (writing MCE handlers is extremly hard because you cannot
    rely on any locking guarantees - even a printk can randomly deadlock)

    For those the per pci_dev callback is the only realistic way.

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

    \
     
     \ /
      Last update: 2005-03-22 14:00    [W:0.026 / U:29.436 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site