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] trace default?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] trace default?
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 7 Sep 2005 17:00:42 +0100
Cc: Rob Gardner <rob.gardner@xxxxxx>
Delivery-date: Wed, 07 Sep 2005 15:59:48 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <431F0B04.6010801@xxxxxx>
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: <431E1D6C.2070308@xxxxxx> <06f142c84884b47a710a8202eff3525f@xxxxxxxxxxxx> <431F0B04.6010801@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
> Yes, but they are likely to stick with the xen defaults unless they have
> a reason for changing them. In the case of tracing,  their reaction is
> likely to be that "tracing" sounds like some debugging feature, will
> probably be bad for performance, so let's leave it turned off. So could
> you state what performance impact you think tracing will actually have
> on the system?

Trace buffers can be disabled on the commandline to avoid the memory overhead 
and the cost of calling the "trace" function itself via the TRACE_xD macros 
should not be measurable.


Xen-devel mailing list

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