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