linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] nmi: create generic NMI backtrace implementation
Date: Thu, 16 Jul 2015 10:37:44 +0100	[thread overview]
Message-ID: <20150716093744.GI7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <55A7753C.9020708@linaro.org>

On Thu, Jul 16, 2015 at 10:11:24AM +0100, Daniel Thompson wrote:
> On 15/07/15 21:39, Russell King wrote:
> >+void nmi_trigger_all_cpu_backtrace(bool include_self,
> >+				   void (*raise)(cpumask_t *mask))
> >+{
> >+	struct nmi_seq_buf *s;
> >+	int i, cpu, this_cpu = get_cpu();
> >+
> >+	if (test_and_set_bit(0, &backtrace_flag)) {
> >+		/*
> >+		 * If there is already a trigger_all_cpu_backtrace() in progress
> >+		 * (backtrace_flag == 1), don't output double cpu dump infos.
> >+		 */
> >+		put_cpu();
> >+		return;
> >+	}
> >+
> >+	cpumask_copy(to_cpumask(backtrace_mask), cpu_online_mask);
> >+	if (!include_self)
> >+		cpumask_clear_cpu(this_cpu, to_cpumask(backtrace_mask));
> >+
> >+	cpumask_copy(&printtrace_mask, to_cpumask(backtrace_mask));
> >+
> >+	/*
> >+	 * Set up per_cpu seq_buf buffers that the NMIs running on the other
> >+	 * CPUs will write to.
> >+	 */
> >+	for_each_cpu(cpu, to_cpumask(backtrace_mask)) {
> >+		s = &per_cpu(nmi_print_seq, cpu);
> >+		seq_buf_init(&s->seq, s->buffer, NMI_BUF_SIZE);
> >+	}
> >+
> >+	if (!cpumask_empty(to_cpumask(backtrace_mask))) {
> >+		pr_info("Sending NMI to %s CPUs:\n",
> >+			(include_self ? "all" : "other"));
> >+		raise(to_cpumask(backtrace_mask));
> 
> On ARM, this code could be running with IRQs locked and with raise()
> implemented using IRQs. In such as case the IPI will not be raised until the
> function exists (and perhaps never). Thanks to the timeout we will exit but
> we end up needlessly failing to print a backtrace for the calling CPU.
> 
> The solution I used for this was to special case the current CPU and call
> nmi_cpu_backtrace() directly. Originally I made this logic arm only but I
> can't really see any reason for this to be arch specific so the logic to do
> that should probably be included here.

That can be implemented in the arch raise() method if needed - most
architectures shouldn't need it as if they are properly raising a NMI
which is, by definition, deliverable with normal IRQs disabled.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-07-16  9:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 20:39 [PATCH 0/3] Shared NMI backtracing support for ARM/x86 Russell King - ARM Linux
2015-07-15 20:39 ` [PATCH 1/3] nmi: create generic NMI backtrace implementation Russell King
2015-07-16  9:11   ` Daniel Thompson
2015-07-16  9:37     ` Russell King - ARM Linux [this message]
2015-07-16  9:51       ` Daniel Thompson
2015-07-25 14:42         ` Russell King - ARM Linux
2015-07-28  8:29           ` Daniel Thompson
2015-07-16 11:07   ` Thomas Gleixner
2015-07-15 20:39 ` [PATCH 2/3] nmi: x86: convert to generic nmi handler Russell King
2015-07-16 11:07   ` Thomas Gleixner
2015-07-15 20:39 ` [PATCH 3/3] ARM: add basic support for on-demand backtrace of other CPUs Russell King
2015-07-16  9:13   ` Daniel Thompson
2015-07-16  9:39     ` Russell King - ARM Linux
2015-07-16  9:55 ` [PATCH 0/3] Shared NMI backtracing support for ARM/x86 Daniel Thompson
2015-07-21  9:34 ` Thomas Gleixner

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=20150716093744.GI7557@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).