From: Matt Fleming <matt@console-pimps.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>, Zhang Rui <rui.zhang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
mingo@elte.hu, acme@redhat.com, ming.m.lin@intel.com, "Brown,
Len" <lenb@kernel.org>
Subject: Re: [PATCH 2/3] introduce intel_rapl driver
Date: Thu, 26 May 2011 11:55:39 +0100 [thread overview]
Message-ID: <20110526105527.GA27748@console-pimps.org> (raw)
In-Reply-To: <1306403003.1200.41.camel@twins>
On Thu, May 26, 2011 at 11:43:23AM +0200, Peter Zijlstra wrote:
>
> That's just wrong.. the reason you're wanting to have this timer is to
> avoid the RAPL MSRs from overflowing and you loosing offsets, right?
>
> But the above is actually forcing the event to create samples on a
> totally unrelated time base.
>
> RAPL should fail to create a sampling event since it doesn't have the
> capability to trigger overflow interrupts based on its events.
>
> If you want a timer, add one, but don't do this.
>
> If you expect you actually want to sample, use this event as part of a
> group and add a sampling event in there and use PERF_FORMAT_GROUP, Matt
> was working on patches to make perf-record capable of this.
Yep, I have some unfinished patches around here somewhere...
*rummage*
OK, they're in this repository on the perf/group-events branch,
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/sh-2.6.git
Obviously since I last touched them in November of last year they're
more than likely not going to apply cleanly to tip, and perhaps more
importantly, I don't think I ever submitted them to LKML for review.
Rui, I'll try to look at your patch series over the weekend and get my
sampling patches into a state where they can be submitted for review
and used by the intel_rapl driver. Does that sound OK?
Or if you want to take a more proactive approach, you're welcome to
finish and submit them ;-)
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-05-26 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 8:34 [PATCH 2/3] introduce intel_rapl driver Zhang Rui
2011-05-26 9:43 ` Peter Zijlstra
2011-05-26 10:21 ` Peter Zijlstra
2011-05-26 10:55 ` Matt Fleming [this message]
2011-06-02 8:04 ` Matt Fleming
2011-05-27 8:26 ` Zhang Rui
2011-05-27 19:56 ` Peter Zijlstra
2011-05-27 19:56 ` Peter Zijlstra
2011-05-30 3:11 ` Zhang Rui
2011-05-26 15:48 ` Randy Dunlap
2011-05-30 2:40 ` Zhang Rui
2011-05-28 10:17 ` Greg KH
2011-05-30 7:04 ` Zhang Rui
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=20110526105527.GA27748@console-pimps.org \
--to=matt@console-pimps.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=rui.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox