All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 2/2] microblaze: allow developer selection of STACKTRACE
@ 2010-04-14  4:55 Steven J. Magnani
  2010-04-14 15:25 ` Michal Simek
  0 siblings, 1 reply; 5+ messages in thread
From: Steven J. Magnani @ 2010-04-14  4:55 UTC (permalink / raw)
  To: microblaze-uclinux; +Cc: monstr, linux-kernel, Steven J. Magnani

Allow the developer to configure STACKTRACE to enable userland access to backtraces in /proc/NN/stack.

Signed-off-by: Steven J. Magnani <steve@digidescorp.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.
+
 endmenu
 
 menu "Advanced setup"



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2/2] microblaze: allow developer selection of STACKTRACE
  2010-04-14  4:55 [PATCH 2/2] microblaze: allow developer selection of STACKTRACE Steven J. Magnani
@ 2010-04-14 15:25 ` Michal Simek
  2010-04-14 15:44   ` Steven J. Magnani
  0 siblings, 1 reply; 5+ messages in thread
From: Michal Simek @ 2010-04-14 15:25 UTC (permalink / raw)
  To: Steven J. Magnani; +Cc: microblaze-uclinux, linux-kernel

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@digidescorp.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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2/2] microblaze: allow developer selection of STACKTRACE
  2010-04-14 15:25 ` Michal Simek
@ 2010-04-14 15:44   ` Steven J. Magnani
  2010-04-14 16:49     ` Michal Simek
  0 siblings, 1 reply; 5+ messages in thread
From: Steven J. Magnani @ 2010-04-14 15:44 UTC (permalink / raw)
  To: monstr; +Cc: microblaze-uclinux, linux-kernel

On Wed, 2010-04-14 at 17:25 +0200, Michal Simek wrote:
> 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@digidescorp.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?

AFAICT STACKTRACE is an embedded option that isn't presented in the
menu. If all you want is /proc/NN/stack without the baggage of kmemleak,
tracing, etc., I didn't see a way to configure it.

This probably belongs somewhere more generic, maybe lib/Kconfig.debug?

Steve



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2/2] microblaze: allow developer selection of STACKTRACE
  2010-04-14 15:44   ` Steven J. Magnani
@ 2010-04-14 16:49     ` Michal Simek
  2010-04-14 16:57       ` Arnd Bergmann
  0 siblings, 1 reply; 5+ messages in thread
From: Michal Simek @ 2010-04-14 16:49 UTC (permalink / raw)
  To: steve; +Cc: microblaze-uclinux, linux-kernel, Arnd Bergmann

Steven J. Magnani wrote:
> On Wed, 2010-04-14 at 17:25 +0200, Michal Simek wrote:
>> 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@digidescorp.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?
> 
> AFAICT STACKTRACE is an embedded option that isn't presented in the
> menu. If all you want is /proc/NN/stack without the baggage of kmemleak,
> tracing, etc., I didn't see a way to configure it.

Agree that you have to enable some option to get this functionality but 
the correct question is if someone need only this functionality.

> 
> This probably belongs somewhere more generic, maybe lib/Kconfig.debug?

It is more generic things.
Arnd: What do you think?

Thanks,
Michal


> 
> Steve
> 
> 


-- 
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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 2/2] microblaze: allow developer selection of STACKTRACE
  2010-04-14 16:49     ` Michal Simek
@ 2010-04-14 16:57       ` Arnd Bergmann
  0 siblings, 0 replies; 5+ messages in thread
From: Arnd Bergmann @ 2010-04-14 16:57 UTC (permalink / raw)
  To: monstr; +Cc: steve, microblaze-uclinux, linux-kernel

On Wednesday 14 April 2010, Michal Simek wrote:
> >>> 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?
> > 
> > AFAICT STACKTRACE is an embedded option that isn't presented in the
> > menu. If all you want is /proc/NN/stack without the baggage of kmemleak,
> > tracing, etc., I didn't see a way to configure it.
> 
> Agree that you have to enable some option to get this functionality but 
> the correct question is if someone need only this functionality.
> 
> > 
> > This probably belongs somewhere more generic, maybe lib/Kconfig.debug?
> 
> It is more generic things.
> Arnd: What do you think?

CONFIG_STACKTRACE is currently  silent option that can be selected by
others. If there is value in having it enabled without any of the others,
just make it an explicit option by adding a text to 'config BACKTRACE'
in lib/Kconfig.debug.

	Arnd

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-04-14 16:58 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-14  4:55 [PATCH 2/2] microblaze: allow developer selection of STACKTRACE Steven J. Magnani
2010-04-14 15:25 ` Michal Simek
2010-04-14 15:44   ` Steven J. Magnani
2010-04-14 16:49     ` Michal Simek
2010-04-14 16:57       ` Arnd Bergmann

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.