From: Andi Kleen <ak@linux.intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "Liang, Kan" <kan.liang@intel.com>,
"acme@kernel.org" <acme@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"eranian@google.com" <eranian@google.com>,
jolsa@kernel.org
Subject: Re: [PATCH 1/1] perf, tool: partial callgrap and time support in perf record
Date: Wed, 18 Mar 2015 12:18:25 -0700 [thread overview]
Message-ID: <20150318191825.GA15335@tassilo.jf.intel.com> (raw)
In-Reply-To: <20150318071406.GS943@sejong>
> > The answer is no: it solves a different problem. Group read
> > is just fine granuality counting. It cannot be used
> > to sample for multiple events in parallel.
>
> But group read disables sampling for non-leader events so the number
> of total samples should be small, no?
Yes it's smaller, but it doesn't sample everything.
-Andi
prev parent reply other threads:[~2015-03-18 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 2:18 [PATCH 1/1] perf, tool: partial callgrap and time support in perf record kan.liang
2015-03-16 2:03 ` Namhyung Kim
2015-03-16 20:35 ` Liang, Kan
2015-03-16 20:48 ` Andi Kleen
2015-03-18 7:14 ` Namhyung Kim
2015-03-18 19:18 ` Andi Kleen [this message]
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=20150318191825.GA15335@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=eranian@google.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