LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: benh@kernel.crashing.org, paulus@samba.org, npiggin@gmail.com,
	xinhui.pan@linux.vnet.ibm.com, gpiccoli@linux.vnet.ibm.com
Subject: Re: [PATCH 2/3] powerpc/xmon: drop the nobt option from xmon plus minor fixes
Date: Tue, 21 Feb 2017 16:16:31 +1100	[thread overview]
Message-ID: <87poicm8cw.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1487290677-7200-3-git-send-email-gpiccoli@linux.vnet.ibm.com>

"Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com> writes:
> Subject: Re: [PATCH 2/3] powerpc/xmon: drop the nobt option from xmon plus minor fixes

In future please use the same version number for all patches of a
series.

ie. This should include a v2, like the rest of the patches in the series.

It confuses the tools to have "v2 1/3" "2/3" "v2 3/3".

I realise that might seem a little odd when a patch is new to the
series, but the version is the version *of the series*, not the
individual patches.

For a new patch you can just add after the change log:

---
v2: New for v2 of the series.


For example.

> The xmon parameter nobt was added long time ago, by commit 26c8af5f01df
> ("[POWERPC] print backtrace when entering xmon"). The problem that time
> was that during a crash in a machine with USB keyboard, xmon wouldn't
> respond to commands from the keyboard, so printing the backtrace wouldn't
> be possible.
>
> Idea then was to show automatically the backtrace on xmon crash for the
> first time it's invoked (if it recovers, next time xmon won't show
> backtrace automatically). The nobt parameter was added _only_ to prevent
> this automatic trace show. Seems long time ago USB keyboards didn't work
> that well!
>
> We don't need it anymore, but the feature of auto showing the backtrace
> on first crash seems interesting (imagine a case of auto-reboot script),
> so this patch keeps the functionality, yet removes the nobt parameter.


I'm going to take this as-is, because I want to get it in for v4.11.

But I don't think we need the auto back trace logic at all. If anything
it's an anti-feature IMHO.

Imagine you're debugging a machine and you drop into xmon to check
something, then drop out again.

Then you go away and leave the box, and it crashes into xmon, but xmon
doesn't print a backtrace because you've already been in xmon. Usually
you can just get on the console and hit 't', but sometimes the machine
crashes so hard that xmon doesn't take input - in which case you now
have no backtrace. :sadface:

So I'll send a follow-up patch to remove the auto backtrace stuff
completely and see if anyone objects.

cheers

  reply	other threads:[~2017-02-21  5:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  0:17 [PATCH 0/3] powerpc/xmon: improvements and fixes Guilherme G. Piccoli
2017-02-17  0:17 ` [PATCH v2 1/3] powerpc/xmon: Fix an unexpected xmon on/off state change Guilherme G. Piccoli
2017-02-17  0:17 ` [PATCH 2/3] powerpc/xmon: drop the nobt option from xmon plus minor fixes Guilherme G. Piccoli
2017-02-21  5:16   ` Michael Ellerman [this message]
2017-02-21  5:33     ` Michael Ellerman
2017-02-21 13:42       ` Guilherme G. Piccoli
2017-02-21 13:41     ` Guilherme G. Piccoli
2017-02-17  0:17 ` [PATCH v2 3/3] powerpc/xmon: add debugfs entry for xmon Guilherme G. Piccoli
2017-02-21  2:01 ` [PATCH 0/3] powerpc/xmon: improvements and fixes Guilherme G. Piccoli
  -- strict thread matches above, loose matches on Subject: below --
2017-02-21  1:58 [PATCH v2 " Guilherme G. Piccoli
2017-02-21  1:58 ` [PATCH 2/3] powerpc/xmon: drop the nobt option from xmon plus minor fixes Guilherme G. Piccoli

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=87poicm8cw.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=gpiccoli@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.org \
    --cc=xinhui.pan@linux.vnet.ibm.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