[lkml]   [2005]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH/RFC] I/O-check interface for driver's error handling
    On So 05-03-05 10:03:37, Benjamin Herrenschmidt wrote:
    > On Fri, 2005-03-04 at 23:57 +0100, Pavel Machek wrote:
    > > What prevents driver from being run on another CPU, maybe just doing
    > > mdelay() between hardware accesses?
    > Almost all drivers that I know have some sort of locking. Nothing nasty
    > about it. Besides, you can't expect everything to be as simple as
    > putting two bit of lego together, the problem isn't simple.

    If error() is allowed to sleep, then yes, its probably easy enough. If
    it is not allowed to sleep, it will just postpone work to context that
    is allowed to sleep, and it will probably be okay, too.

    => there are some locking issues, but they are probably easy
    enough. Sorry for noise.

    People were complaining that M$ turns users into beta-testers...
    ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
    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-03-22 14:10    [W:0.019 / U:1.904 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site