Message-ID: <4BC5F20F.3050108@monstr.eu>
Date: Wed, 14 Apr 2010 18:49:19 +0200
From: Michal Simek <monstr@monstr.eu>
Reply-To: monstr@monstr.eu
User-Agent: Thunderbird 2.0.0.22 (X11/20090625)
MIME-Version: 1.0
To: steve@digidescorp.com
CC: microblaze-uclinux@itee.uq.edu.au, linux-kernel@vger.kernel.org,
       Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/2] microblaze: allow developer selection of STACKTRACE
References: <1271220938-3526-1-git-send-email-steve@digidescorp.com>	 <4BC5DE54.2010305@monstr.eu> <1271259851.2990.20.camel@iscandar.digidescorp.com>
In-Reply-To: <1271259851.2990.20.camel@iscandar.digidescorp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2068
Lines: 60

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/