This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap pa

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: [Xen-devel] Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt ops callsites to make them patchable
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 20 Mar 2007 21:39:18 +0000
Cc: jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Andi, David Miller <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxxxxxx, Kleen <ak@xxxxxxx>, jbeulich@xxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, chrisw@xxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>, anthony@xxxxxxxxxxxxx, mingo@xxxxxxx, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, akpm@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Mar 2007 13:35:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070320202352.GF4286@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070319.204712.118947830.davem@xxxxxxxxxxxxx> <m13b40wnrb.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx> <200703201428.50564.ak@xxxxxxx> <m1ircvswzz.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx> <20070320174159.GA4286@xxxxxxxxxxxxxx> <Pine.LNX.4.64.0703200947501.6730@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20070320180359.GB4286@xxxxxxxxxxxxxx> <Pine.LNX.4.64.0703201022040.6730@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20070320192118.GD4286@xxxxxxxxxxxxxx> <Pine.LNX.4.64.0703201145570.6730@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20070320202352.GF4286@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > 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


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>