> - 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. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
