[lkml]   [2008]   [Feb]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [git pull] kgdb-light -v10
    >  - the kgdb commands should always act on the *current* CPU only
    > - add one command that says "switch over to CPU #n" which just releases
    > the current CPU and sends an IPI to that CPU #n (no timeouts, no
    > synchronous waiting, no nothing - it's like a "continue", but with a
    > "try to get the other CPU to stop"

    The problem I see here is that the kernel tends to get badly confused
    if one CPU just stops responding. At some point someone does an global
    IPI and that then hangs. You would need to hotunplug the CPU which
    is theoretically possible, but quite intrusive. Or maybe the "isolate CPUs
    in cpusets" frame work someone posted recently on l-k could be used. Still
    would probably have all kinds of tricky issues and races.


     \ /
      Last update: 2008-02-12 18:47    [W:0.046 / U:8.724 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site