WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [PATCH] [Xen-devel] trace default?

For arguments' sake I'm attaching a (build tested, hg import-able) changeset I 
knocked up to unconditionally enable the trace buffer.  The default size is 
10 pages / online CPU (runtime configurable).

Cheers,
Mark

> > 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.
>
> Cheers,
> Mark
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Attachment: trace-enable.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>