lkml.org 
[lkml]   [2008]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [2/2] vmallocinfo: Add caller information
    On Tue, Apr 29, 2008 at 10:09 PM, Christoph Lameter <clameter@sgi.com> wrote:
    > Well so we display out of whack backtraces? There are also issues on
    > platforms that do not have a stack in the classic sense (rotating register
    > file on IA64 and Sparc64 f.e.). Determining a backtrace can be very
    > expensive.

    I think that's the key question here whether we need to enable this on
    production systems? If yes, why? If it's just a debugging aid, then I
    see Ingo's point of save_stack_trace(); otherwise the low-overhead
    __builtin_return_address() makes more sense.

    And btw, why is this new file not in /sys/kernel....?


    \
     
     \ /
      Last update: 2008-04-29 21:25    [W:2.200 / U:0.304 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site