[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BC5DE54.2010305@monstr.eu>
Date: Wed, 14 Apr 2010 17:25:08 +0200
From: Michal Simek <monstr@...str.eu>
To: "Steven J. Magnani" <steve@...idescorp.com>
CC: microblaze-uclinux@...e.uq.edu.au, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] microblaze: allow developer selection of STACKTRACE
Steven J. Magnani wrote:
> Allow the developer to configure STACKTRACE to enable userland access to backtraces in /proc/NN/stack.
>
> Signed-off-by: Steven J. Magnani <steve@...idescorp.com>
> ---
> diff -uprN a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig
> --- a/arch/microblaze/Kconfig 2010-04-09 21:52:36.000000000 -0500
> +++ b/arch/microblaze/Kconfig 2010-04-12 22:16:01.000000000 -0500
> @@ -136,6 +136,14 @@ config PROC_DEVICETREE
> an image of the device tree that the kernel copies from Open
> Firmware or other boot firmware. If unsure, say Y here.
>
> +config PROC_BACKTRACE
> + bool "Support for kernel backtraces in /proc/NN/stack"
> + default n
> + select STACKTRACE
> + help
> + This option adds a backtrace of the kernel stack to /proc/NN/stack.
> + If unsure, say N here.
> +
Why did you create new Kconfig option? /proc/NN/stack is there when you
enable stacktrace support. There is not necessary to enable any new option.
Or is there any other point which I am missing?
Thanks,
Michal
> endmenu
>
> menu "Advanced setup"
>
>
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists