All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: trace default?
Date: Wed, 07 Sep 2005 09:45:08 -0600	[thread overview]
Message-ID: <431F0B04.6010801@hp.com> (raw)
In-Reply-To: <06f142c84884b47a710a8202eff3525f@cl.cam.ac.uk>

Keir Fraser wrote:

>
> On 6 Sep 2005, at 23:51, Rob Gardner wrote:
>
>> The xen trace facility is not enabled by default. I'm working on some 
>> tools that use it, and I'm concerned that the tool will not work for 
>> customers who buy packaged distro's. What are the arguments for 
>> keeping trace disabled? Is it just the memory consumed by the trace 
>> buffers? It doesn't appear to me that there would be any impact 
>> beyond that. What is the possibility of making tracing enabled by 
>> default?
>
>
> It's up to the distros to decide what options they anable in their 
> default Xen package imo.


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?

Thanks,
Rob

  reply	other threads:[~2005-09-07 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 22:51 trace default? Rob Gardner
2005-09-07  9:48 ` Keir Fraser
2005-09-07 15:45   ` Rob Gardner [this message]
2005-09-07 16:00     ` Mark Williamson
2005-09-07 16:54       ` [PATCH] " Mark Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=431F0B04.6010801@hp.com \
    --to=rob.gardner@hp.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.