From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, acme@redhat.com, jolsa@redhat.com,
namhyung.kim@lge.com
Subject: Re: [PATCH v5 0/2] perf: use hrtimer for event multiplexing
Date: Fri, 22 Mar 2013 10:33:26 -0700 [thread overview]
Message-ID: <20130322173326.GN19692@tassilo.jf.intel.com> (raw)
In-Reply-To: <1363949499-3728-1-git-send-email-eranian@google.com>
On Fri, Mar 22, 2013 at 11:51:37AM +0100, Stephane Eranian wrote:
> The current scheme of using the timer tick was fine
> for per-thread events. However, it was causing
> bias issues in system-wide mode (including for
> uncore PMUs). Event groups would not get their
> fair share of runtime on the PMU. With tickless
> kernels, if a core is idle there is no timer tick,
> and thus no event rotation (multiplexing). However,
> there are events (especially uncore events) which do
> count even though cores are asleep.
Would it be possible to only do this when uncore events
are active? Otherwise it may have a large power cost
and actually change results, as the core counters
will tick more.
-Andi
next prev parent reply other threads:[~2013-03-22 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 10:51 Stephane Eranian
2013-03-22 10:51 ` [PATCH v5 1/2] " Stephane Eranian
2013-03-25 11:13 ` Peter Zijlstra
2013-03-25 17:58 ` Stephane Eranian
2013-03-22 10:51 ` [PATCH v5 2/2] perf: add sysfs entry to adjust multiplexing interval per PMU Stephane Eranian
2013-03-25 11:43 ` Peter Zijlstra
2013-03-25 12:15 ` Stephane Eranian
2013-03-22 13:54 ` [PATCH v5 0/2] perf: use hrtimer for event multiplexing Frederic Weisbecker
2013-03-25 12:08 ` Peter Zijlstra
2013-03-25 12:21 ` Frederic Weisbecker
2013-03-22 17:33 ` Andi Kleen [this message]
2013-03-22 17:36 ` Stephane Eranian
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=20130322173326.GN19692@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=peterz@infradead.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
Powered by JetHome