From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/dumpstack: make stack name tags more comprehensible
Date: Fri, 18 Nov 2016 19:54:25 +0100 [thread overview]
Message-ID: <20161118185425.GX3117@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <180196e3754572540b595bc56b947d43658979a7.1479491159.git.jpoimboe@redhat.com>
On Fri, Nov 18, 2016 at 11:46:23AM -0600, Josh Poimboeuf wrote:
> NMI stack dumps are bracked by the following tags:
>
> <NMI>
> ...
> <EOE>
>
> The ending tag is kind of confusing if you don't already know what "EOE"
> means (end of exception). The same ending tag is also used to mark the
> end of all other exceptions' stacks. For example:
>
> <#DF>
> ...
> <EOE>
>
> And similarly, "EOI" is used as the ending tag for interrupts:
>
> <IRQ>
> ...
> <EOI>
>
> Change the tags to be more comprehensible by making them symmetrical and
> more XML-esque:
>
> <NMI>
> ...
> </NMI>
>
> <#DF>
> ...
> </#DF>
>
> <IRQ>
> ...
> </IRQ>
>
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
> arch/x86/include/asm/stacktrace.h | 3 +--
> arch/x86/kernel/dumpstack.c | 12 ++++++------
> arch/x86/kernel/dumpstack_32.c | 19 ++++++++-----------
> arch/x86/kernel/dumpstack_64.c | 22 ++++++++--------------
> 4 files changed, 23 insertions(+), 33 deletions(-)
And saves lines too, awesome!
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2016-11-18 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 17:46 Josh Poimboeuf
2016-11-18 18:54 ` Peter Zijlstra [this message]
2016-11-19 15:49 ` Frederic Weisbecker
2016-11-19 20:25 ` Josh Poimboeuf
2016-11-21 10:38 ` [tip:x86/asm] x86/dumpstack: Make " tip-bot for Josh Poimboeuf
2016-11-21 12:07 ` tip-bot for Josh Poimboeuf
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=20161118185425.GX3117@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome