Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754111AbcCAOXi (ORCPT ); Tue, 1 Mar 2016 09:23:38 -0500 Received: from mail-wm0-f42.google.com ([74.125.82.42]:36819 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752636AbcCAOXh (ORCPT ); Tue, 1 Mar 2016 09:23:37 -0500 Subject: Re: [PATCH 2/4] nmi_backtrace: generate one-line reports for idle cpus To: Chris Metcalf References: <1456782024-7122-1-git-send-email-cmetcalf@ezchip.com> <1456782024-7122-3-git-send-email-cmetcalf@ezchip.com> From: Daniel Thompson Cc: Russell King , Thomas Gleixner , Ingo Molnar , Andrew Morton , linux-kernel@vger.kernel.org, Aaron Tomlin Message-ID: <56D5A5E6.9050206@linaro.org> Date: Tue, 1 Mar 2016 14:23:34 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <1456782024-7122-3-git-send-email-cmetcalf@ezchip.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 553 Lines: 14 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.