Re: [RFC][PATCH 0/3] x86/nmi: Print all cpu stacks from NMI safely

Jiri Kosina
2014-06-25T10:01:55Z

On Tue, 24 Jun 2014, Konstantin Khlebnikov wrote:

> Originally I thought that seizing all cpus one by one and printing from
> the initiator is a best approach and I've started preparing arguments
> against over-engineered printk...

By "seizing" I guess you mean sending IPI, right?

What do you do if you'd interrupt it in the middle of printk() in order
not to deadlock by trying to take the buffer lock on the initiator CPU?

--
Jiri Kosina
SUSE Labs