[lkml]   [2002]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Preempt note in the logs

    On 24 Aug 2002, Robert Love wrote:
    > It is caused by any mismatched locking - it is a good debugging check
    > regardless of preemption.

    Do you think it's useful to temporarily put a lock counter into struct
    task (TEMPORARILY, Linus, temporarily!) and check that as well? Maybe that
    will point us something.

    Or we should extend that whole crap a bit so we could see exactly what
    caused the preemption count to rise. I don't know if we can do that, but
    we can try doing that.

    --./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .-
    --/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..-
    .- -/---/--/---/.-./.-./---/.--/.-.-.-

    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 13:28    [W:5.698 / U:2.136 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site