From: Petr Mladek <pmladek@suse.com>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Aaron Tomlin <atomlin@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@osdl.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
x86@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v9 4/4] nmi_backtrace: generate one-line reports for idle cpus
Date: Tue, 30 Aug 2016 17:46:41 +0200 [thread overview]
Message-ID: <20160830154641.GD4554@pathway.suse.cz> (raw)
In-Reply-To: <1472487169-14923-5-git-send-email-cmetcalf@mellanox.com>
On Mon 2016-08-29 12:12:49, Chris Metcalf wrote:
> When doing an nmi backtrace of many cores, most of which 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: idling at pc 0xNNN".
>
> We do this by grouping all the cpuidle code together into a new
> .cpuidle.text section, and then checking the address of the
> interrupted PC to see if it lies within that section.
>
> This commit suitably tags x86 and tile idle routines, and only
> adds in the minimal framework for other architectures.
>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Tested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Tested-by: Daniel Thompson <daniel.thompson@linaro.org> [arm]
> Signed-off-by: Chris Metcalf <cmetcalf@mellanox.com>
This version works even with my configuration. Feel free to
add
Tested-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: pmladek@suse.com (Petr Mladek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 4/4] nmi_backtrace: generate one-line reports for idle cpus
Date: Tue, 30 Aug 2016 17:46:41 +0200 [thread overview]
Message-ID: <20160830154641.GD4554@pathway.suse.cz> (raw)
In-Reply-To: <1472487169-14923-5-git-send-email-cmetcalf@mellanox.com>
On Mon 2016-08-29 12:12:49, Chris Metcalf wrote:
> When doing an nmi backtrace of many cores, most of which 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: idling at pc 0xNNN".
>
> We do this by grouping all the cpuidle code together into a new
> .cpuidle.text section, and then checking the address of the
> interrupted PC to see if it lies within that section.
>
> This commit suitably tags x86 and tile idle routines, and only
> adds in the minimal framework for other architectures.
>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Tested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Tested-by: Daniel Thompson <daniel.thompson@linaro.org> [arm]
> Signed-off-by: Chris Metcalf <cmetcalf@mellanox.com>
This version works even with my configuration. Feel free to
add
Tested-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2016-08-30 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1472487169-14923-1-git-send-email-cmetcalf@mellanox.com>
2016-08-29 16:12 ` [PATCH v9 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods Chris Metcalf
2016-08-29 16:12 ` Chris Metcalf
2016-08-29 16:12 ` Chris Metcalf
2016-08-29 16:12 ` [PATCH v9 2/4] nmi_backtrace: do a local dump_stack() instead of a self-NMI Chris Metcalf
2016-08-29 16:12 ` Chris Metcalf
2016-08-29 16:12 ` [PATCH v9 3/4] arch/tile: adopt the new nmi_backtrace framework Chris Metcalf
2016-08-29 16:12 ` [PATCH v9 4/4] nmi_backtrace: generate one-line reports for idle cpus Chris Metcalf
2016-08-29 16:12 ` Chris Metcalf
2016-08-30 15:46 ` Petr Mladek [this message]
2016-08-30 15:46 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160830154641.GD4554@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@osdl.org \
--cc=atomlin@redhat.com \
--cc=cmetcalf@mellanox.com \
--cc=daniel.thompson@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.