From: Ingo Molnar <mingo@kernel.org>
To: George Beshers <gbeshers@sgi.com>
Cc: Mike Travis <travis@sgi.com>,
linux-kernel@vger.kernel.org, Alex Thorlton <athorlton@sgi.com>,
Dimitri Sivanich <sivanich@sgi.com>,
Ingo Molnar <mingo@redhat.com>, Hedi Berriche <hedi@sgi.com>,
Russ Anderson <rja@sgi.com>
Subject: Re: [PATCH 2/2] UV: NMI: simple dump failover if kdump fails
Date: Fri, 1 May 2015 09:27:33 +0200 [thread overview]
Message-ID: <20150501072733.GD19852@gmail.com> (raw)
In-Reply-To: <20150430132919.28122.53176.sendpatchset@gulag2.americas.sgi.com>
* George Beshers <gbeshers@sgi.com> wrote:
> UV: NMI: simple dump failover if kdump fails
>
> The ability to trigger a kdump using the system NMI command
> was added by
>
> commit 12ba6c990fab50fe568f3ad8715e81e356552428
> Author: Mike Travis <travis@sgi.com>
> Date: Mon Sep 23 16:25:03 2013 -0500
>
> When kdump is works it is preferable to the set of backtraces
(spelling error)
> that dump provides; however a number of things can go wrong and
> the backtraces are much more useful than nothing.
>
> The two most common reason for kdump not to be available are
(spelling error)
> a problem during boot or the kdump daemon fails to start.
(spelling error)
> In either case the call to crash_kexec() returns unexpectedly;
> when this happens uv_nmi_kdump() also returns with the
> uv_nmi_kexec_failed flag set. This condition now causes a
> standard dump.
'standard dump' == printing an NMI backtrace on all CPUs?
> One other minor change is that dump now generates both the
> show_regs() stack trace and the uv_nmi_dump_ip{,_hdr} information
> that is generated by the "ips" action; the additional information
> has proved to be useful.
Looks like a useful change.
> -/* Dump this cpu's state */
> +/*
> + * Dump this cpu's state. Note that "kdump" only happens
s/CPU's
> + * when crash_kexec() has failed and we are providing the user
> + * a standard dump instead.
So this sentence does not parse for me: kdump only happens if kdump
fails??
> + */
> static void uv_nmi_dump_state_cpu(int cpu, struct pt_regs *regs)
> {
> const char *dots = " ................................. ";
>
> - if (uv_nmi_action_is("ips")) {
> - if (cpu == 0)
> - uv_nmi_dump_cpu_ip_hdr();
> -
> - if (current->pid != 0)
> - uv_nmi_dump_cpu_ip(cpu, regs);
> -
> - } else if (uv_nmi_action_is("dump")) {
> + if (uv_nmi_action_is("dump") || uv_nmi_action_is("kdump")) {
> printk(KERN_DEFAULT
> "UV:%sNMI process trace for CPU %d\n", dots, cpu);
pr_info().
> show_regs(regs);
> }
> +
> + if (cpu == 0)
> + uv_nmi_dump_cpu_ip_hdr();
> +
> + if (current->pid != 0)
> + uv_nmi_dump_cpu_ip(cpu, regs);
What is an 'ip header'? If it's not an Internet IP address then it's
probably horribly named.
> +
> +#if defined(CONFIG_KEXEC)
#ifdef
> @@ -502,9 +507,9 @@ static void uv_nmi_kdump(int cpu, int master, struct pt_regs *regs)
> crash_kexec(regs);
>
> pr_emerg("UV: crash_kexec unexpectedly returned, ");
> + atomic_set(&uv_nmi_kexec_failed, 1);
Why is this flag an atomic variable?
Thanks,
Ingo
next prev parent reply other threads:[~2015-05-01 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 13:29 [PATCH 1/2] UV: NMI: insert per_cpu accessor function on uv_hub_nmi George Beshers
2015-04-30 13:29 ` [PATCH 2/2] UV: NMI: simple dump failover if kdump fails George Beshers
2015-05-01 7:27 ` Ingo Molnar [this message]
2015-05-01 16:33 ` Mike Travis
2015-05-01 16:42 ` Ingo Molnar
2015-05-01 7:21 ` [PATCH 1/2] UV: NMI: insert per_cpu accessor function on uv_hub_nmi Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2015-09-13 2:51 George Beshers
2015-09-13 2:51 ` [PATCH 2/2] UV: NMI: simple dump failover if kdump fails George Beshers
2015-09-13 7:23 ` Ingo Molnar
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=20150501072733.GD19852@gmail.com \
--to=mingo@kernel.org \
--cc=athorlton@sgi.com \
--cc=gbeshers@sgi.com \
--cc=hedi@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--cc=sivanich@sgi.com \
--cc=travis@sgi.com \
/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