[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56D5A5E6.9050206@linaro.org>
Date: Tue, 1 Mar 2016 14:23:34 +0000
From: Daniel Thompson <daniel.thompson@...aro.org>
To: Chris Metcalf <cmetcalf@...hip.com>
Cc: Russell King <linux@....linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Andrew Morton <akpm@...l.org>,
linux-kernel@...r.kernel.org, Aaron Tomlin <atomlin@...hat.com>
Subject: Re: [PATCH 2/4] nmi_backtrace: generate one-line reports for idle
cpus
On 29/02/16 21:40, Chris Metcalf wrote:
> When doing an nmi backtrace of many cores, and most of them are idle,
> the output is a little overwhelming and very uninformative. Suppress
> messages for cpus that are idling when they are interrupted and
> just emit one line, "NMI backtrace for N skipped: idle".
I can see this makes the logs more attractive but this is code for
emergency situations.
The idle task is responsible for certain power management activities.
How can you be sure the system is wedged because of bugs in that code?
Daniel.
Powered by blists - more mailing lists