lkml.org 
[lkml]   [2007]   [Mar]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [Xen-devel] Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt ops callsites to make them patchable
    > > Because that's really the issue: do you want a "pretty" backtrace, or do 
    > > you want one that is rock solid but has some crud in it.
    >
    > I just want an as exact backtrace as possible. I also think
    > that we can make the unwinder robust enough.

    Any reason you can't put the exact back trace in "[xxx]" and the ones we
    see on the stack which dont look like call trace as ?xxx? It makes the
    code a bit trickier but we depend on the quality of traces

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

    \
     
     \ /
      Last update: 2007-03-20 21:41    [W:4.287 / U:0.232 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site