From: Blue Swirl <blauwirbel@gmail.com>
To: Lluís <xscript@gmx.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/3] trace: enable all events by default
Date: Wed, 10 Nov 2010 17:21:25 +0000 [thread overview]
Message-ID: <AANLkTimJB+NEHui9BghWJf3sESz724hqj-O_Lfj4oreW@mail.gmail.com> (raw)
In-Reply-To: <20101109140848.29831.72280.stgit@ginnungagap.bsc.es>
On Tue, Nov 9, 2010 at 2:08 PM, Lluís <xscript@gmx.net> wrote:
> Enable all trace events by default, assuming their frequency is relatively low,
> so there will be no measurable performace impact.
Even if the impact for one tracepoint is low, if all tracepoints are
enabled, eventually (considering that the number of tracepoints will
increase) just the data flow to the trace file will start to slow down
the guest.
But I'm not completely opposed to removing 'disable' keyword, for
example by turning all tracepoints off initially. Though then there
would be no way to trace the initialization activities.
next prev parent reply other threads:[~2010-11-10 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 14:08 [Qemu-devel] [PATCH v2 1/3] trace: [ust] fix generation of 'trace.c' on events without args Lluís
2010-11-09 14:08 ` [Qemu-devel] [PATCH v2 2/3] trace: always use the "nop" backend on events with the "disable" keyword Lluís
2010-11-09 14:08 ` [Qemu-devel] [PATCH v2 3/3] trace: enable all events by default Lluís
2010-11-10 17:21 ` Blue Swirl [this message]
2010-11-10 17:59 ` Lluís
2010-11-10 18:22 ` Blue Swirl
2010-11-10 19:57 ` Lluís
2010-11-10 20:23 ` Blue Swirl
2010-11-10 21:20 ` Lluís
2010-11-11 9:31 ` Stefan Hajnoczi
2010-11-16 17:03 ` Stefan Hajnoczi
2010-11-17 12:04 ` Lluís
2010-11-09 14:17 ` [Qemu-devel] [PATCH v2 1/3] trace: [ust] fix generation of 'trace.c' on events without args Stefan Hajnoczi
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=AANLkTimJB+NEHui9BghWJf3sESz724hqj-O_Lfj4oreW@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=xscript@gmx.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).