From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, ak@linux.intel.com,
zheng.z.yan@intel.com, robert.richter@amd.com
Subject: Re: [PATCH 1/3] perf: use hrtimer for event multiplexing
Date: Fri, 07 Sep 2012 21:08:51 +0200 [thread overview]
Message-ID: <1347044931.2124.5.camel@twins> (raw)
In-Reply-To: <CABPqkBT=2H5WuWZ+uFq39XTTxniVvT6tEuaYDHvaV2VSbjBPDQ@mail.gmail.com>
On Fri, 2012-09-07 at 19:03 +0200, Stephane Eranian wrote:
> I think having different intervals would be a good thing, especially for uncore.
> But now, I am wondering how this could work without too much overhead.
> Looks like you're suggesting arming multiple hrtimers if multiple PMU are
> overcommitted. Is that right?
Right, we shoulnd't have too many PMUs anyway, let alone over committed
ones, so a timer per cpu per pmu should be fine.
> As opposed to having a PMU multiplier off of a
> single per-cpu hrtimer.
next prev parent reply other threads:[~2012-09-07 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 14:29 [PATCH 0/3] perf: use hrtimer for event multiplexing Stephane Eranian
2012-09-07 14:29 ` [PATCH 1/3] " Stephane Eranian
2012-09-07 15:39 ` Peter Zijlstra
2012-09-07 17:03 ` Stephane Eranian
2012-09-07 19:08 ` Peter Zijlstra [this message]
2012-09-07 19:10 ` Stephane Eranian
2012-09-07 19:14 ` Peter Zijlstra
2012-09-07 15:42 ` Peter Zijlstra
2012-09-07 14:29 ` [PATCH 2/3] perf: add sysctl control to adjust multiplexing interval Stephane Eranian
2012-09-07 14:29 ` [PATCH 3/3] perf: remove jiffies_interval Stephane Eranian
2012-09-07 15:40 ` Peter Zijlstra
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=1347044931.2124.5.camel@twins \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=zheng.z.yan@intel.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.