On 11/12/15 23:26, Jiri Kosina wrote:
On Fri, 11 Dec 2015, Russell King - ARM Linux wrote:
I'm personally happy with the existing code, and I've been wondering why
there's this effort to apply further cleanups - to me, the changelogs
don't seem to make that much sense, unless we want to start using
printk() extensively in NMI functions - using the generic nmi backtrace
code surely gets us something that works across all architectures...
It is already being used extensively, and not only for all-CPU backtraces.
For starters, please consider
- WARN_ON(in_nmi())
- BUG_ON(in_nmi())
Sorry to join in so late but...
Today we risk deadlock when we try to issue these diagnostic errors
directly from NMI context.
After this change we will still risk deadlock, because that's what the
diagnostic code is trying to tell us, *and* we delay actually reporting
the error until, and only if, the NMI handler completes.
I'm not entirely sure that this is an improvement.
- anything being printed out from MCE handlers
The MCE handlers should only call printk() when they decide to panic and
*after* busting the spinlocks. At this point deferring printk() until it
is safe is not very helpful.
When we bust the spinlocks we should probably restore the normal
printk() function to give best chance of the failure messages making it out.
Daniel.
--
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/
