From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@intel.com
Cc: acme@kernel.org, jolsa@kernel.org, namhyung@kernel.org,
ak@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V2 3/5] perf,tool: partial time support
Date: Sun, 12 Jul 2015 15:22:25 +0200 [thread overview]
Message-ID: <20150712132225.GA1687@krava.redhat.com> (raw)
In-Reply-To: <1436264345-12085-4-git-send-email-kan.liang@intel.com>
On Tue, Jul 07, 2015 at 06:19:03AM -0400, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.com>
>
> When multiple events are sampled it may not be needed to collect fine
> grained time stamps on all events. The sample sites are usually nearby.
> It's enough to have time stamps on the regular reference events.
> This patchkit adds the ability to turn off time stamps per event. This
> in term can reduce sampling overhead and the size of the perf.data.
how is this usable in some perf example? I dont get the correlation
between 'refference' and the rest of the events in the report time..
thanks,
jirka
next prev parent reply other threads:[~2015-07-12 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 10:19 [PATCH RFC V2 0/5] partial callgrap and time support kan.liang
2015-07-07 10:19 ` [PATCH RFC V2 1/5] perf,tools: introduce OPT_CALLBACK_SET/OPT_CALLBACK_NOOPT_SET kan.liang
2015-07-08 14:41 ` Jiri Olsa
2015-07-07 10:19 ` [PATCH RFC V2 2/5] perf/documentation: Add description for period kan.liang
2015-07-07 10:19 ` [PATCH RFC V2 3/5] perf,tool: partial time support kan.liang
2015-07-08 14:48 ` Jiri Olsa
2015-07-12 13:22 ` Jiri Olsa [this message]
2015-07-13 18:59 ` Liang, Kan
2015-07-07 10:19 ` [PATCH RFC V2 4/5] perf,tool: partial callgrap support kan.liang
2015-07-07 10:19 ` [PATCH RFC V2 5/5] perf,tests: Add tests to callgrap and time parse kan.liang
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=20150712132225.GA1687@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
/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