* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > In other words, is it perhaps possible to just *get*rid*of* that
> > "kgdb_active" and "nmicallback" and the whole multi-CPU roundup?
> > Just use a kgdb spinlock around the stuff that actually sends and
> > receives individual packets, and expect the debugger side to sort
> > them out (yeah, I suspect this involves having to add the CPU ID to
> > each packet).
>
> i actually think that the notion of "stopping all system state" is
> rather intuitive from a debugging POV: when you have a bug trigger
> somewhere then getting an NMI to all CPUs and stopping them dead in
> their tracks preserves us the system in its most useful state.
on a second thought - i actually think it's rather possible and
straightforward to do what you suggest. Stopping of all CPUs is still
useful, but should be an optional property. I'll play with this a bit
and see how GDB reacts.
Ingo
--
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/
