cpus_in_xmon questions

Anton Blanchard anton at samba.org
Thu Aug 28 01:10:45 EST 2003

> xmon should do something similar.  When a machine croaks on one CPU, its
> often/usually interesting to know what the other CPU's are doing.   That is,
> typically all the cpu's in the complex are involved in some sort lock
> contention, and its pointless to let the other cpus 'keep going' while
> one is stopped.

You can always stop all other cpus if required with ci and jump between
them with c0, c1 etc. I disagree its pointless to let the other cpus
keep going, Ive debugged problems where the other cpus continue
on fine :)

I prefer to poke around on the local cpu before doing the IPI to stop
all cpus. Its safer that way, and xmon is all about being simple so its
hopefully bulletproof. (A number of changes in the ppc64 version have
made it less so, but those bits are slowly being fixed)


** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/

More information about the Linuxppc64-dev mailing list