Re: [PATCH] sysrq: freeze other CPUs during sysrq-t

[Gary Shi]

On 8/16/08, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Why not use stop_machine()?

Just know about  stop_machine() from your reply. Thanx. But after
checking its src, I feel its too demanding to fit sysrq-t use; e.g.,
when other cpus got deadlocked on some spin locks with preempt
disabled, then the kernel threads of stopmachine won't get a chance to
run on other cpus.

We would expect one or more cpus response only to irqs, when we try to
collect sysrq data; most of the  time, only when the systems hang for
whatever reasons does the sysrq data need to be collected, right?

--gys
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/