mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: don't save unreliable stack trace entries
Date: Fri, 22 Feb 2008 10:48:28 -0800	[thread overview]
Message-ID: <20080222104828.3006cd1d@laptopd505.fenrus.org> (raw)
In-Reply-To: <47BF17F5.4040605@gmail.com>

On Fri, 22 Feb 2008 19:44:05 +0100
Vegard Nossum <vegard.nossum@gmail.com> wrote:

> I find the following patch to make saved stack traces so much easier
> to decipher. There might be other uses of save_stack_trace() that I
> am not aware of, though. Also, I suggest changing the underlying
> struct stack_trace to include the reliable/unreliable information.
> This, however, requires all users of save_stack_trace() and all
> arches saving this information to change.
> 
> Kind regards,
> Vegard Nossum
> 
> 
>  From 5edfd896c5f0d728111df3d8cae729a375f29d3c Mon Sep 17 00:00:00
> 2001 From: Vegard Nossum <vegard.nossum@gmail.com>
> Date: Fri, 22 Feb 2008 19:23:58 +0100
> Subject: [PATCH] x86: don't save unreliable stack trace entries
> 
> Currently, there is no way for print_stack_trace() to determine
> whether a given stack trace entry was deemed reliable or not, simply
> because save_stack_trace() does not record this information. (Perhaps
> needless to say, this makes the saved stack traces A LOT harder to
> read, and probably with no other benefits, since debugging features
> that use save_stack_trace() most likely also require frame pointers,
> etc.)
> 
> This patch reverts to the old behaviour of only recording the
> reliable trace entries for saved stack traces.
> 
> Signed-off-by: Vegard Nossum <vegardno@ifi.uio.no>
> ---
>   arch/x86/kernel/stacktrace.c |    4 ++++
>   1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/x86/kernel/stacktrace.c
> b/arch/x86/kernel/stacktrace.c index 02f0f61..c28c342 100644
> --- a/arch/x86/kernel/stacktrace.c
> +++ b/arch/x86/kernel/stacktrace.c
> @@ -25,6 +25,8 @@ static int save_stack_stack(void *data, char *name)
>   static void save_stack_address(void *data, unsigned long addr, int
> reliable) {
>   	struct stack_trace *trace = data;
> +	if (!reliable)
> +		return;
>   	if (trace->skip > 0) {
>   		trace->skip--;
>   		return;
> @@ -37,6 +39,8 @@ static void
>   save_stack_address_nosched(void *data, unsigned long addr, int
> reliable) {
>   	struct stack_trace *trace = (struct stack_trace *)data;
> +	if (!reliable)
> +		return;
>   	if (in_sched_functions(addr))
>   		return;
>   	if (trace->skip > 0) {


I was about to make a patch for this second chunk myself and submit it, so
for the second chunk a strong:
Acked-by: Arjan van de Ven <arjan@linux.intel.com>

Thanks for beating me to it ;-)

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-02-22 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 18:44 Vegard Nossum
2008-02-22 18:48 ` Arjan van de Ven [this message]
2008-02-23 10:25   ` 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=20080222104828.3006cd1d@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vegard.nossum@gmail.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

all inboxes | Powered by JetHome®