From: stephane eranian <eranian@googlemail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
perfmon2-devel@lists.sf.net, linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>,
paulus@samba.org, mingo@elte.hu, davem@davemloft.net
Subject: Re: [perfmon2] [PATCH] perf: fix the is_software_event() definition
Date: Mon, 18 Jan 2010 14:46:21 +0100 [thread overview]
Message-ID: <7c86c4471001180546v74ac3b16ia8c7cadf2a030204@mail.gmail.com> (raw)
In-Reply-To: <1263817164.4283.394.camel@laptop>
On Mon, Jan 18, 2010 at 1:19 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, 2010-01-18 at 13:07 +0100, Frederic Weisbecker wrote:
>
>> Agreed.
>>
>> But then Stephane will need to update his patch and use
>> something else than is_software_event() to guess if an event
>> needs its pmu->enable/disable to be called.
>
> Yes, that's what I told him before and even send a patch for, the name I
> chose was is_x86_event().
>
Yes, I remember that. I will modify the patch to use a function like that.
I think the PPC code would need to be updated similarly.
next prev parent reply other threads:[~2010-01-18 13:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 10:50 [PATCH] perf_events: improve x86 event scheduling Stephane Eranian
2010-01-12 16:10 ` Peter Zijlstra
2010-01-13 9:54 ` Stephane Eranian
2010-01-13 16:29 ` Peter Zijlstra
2010-01-13 16:52 ` Stephane Eranian
2010-01-13 17:22 ` Stephane Eranian
2010-01-17 14:12 ` Frederic Weisbecker
2010-01-17 14:42 ` Stephane Eranian
2010-01-17 16:19 ` Frederic Weisbecker
2010-01-17 21:53 ` Stephane Eranian
2010-01-18 11:13 ` Peter Zijlstra
2010-01-18 11:53 ` [PATCH] perf: fix the is_software_event() definition Peter Zijlstra
2010-01-18 12:07 ` Frederic Weisbecker
2010-01-18 12:19 ` Peter Zijlstra
2010-01-18 13:46 ` stephane eranian [this message]
2010-01-18 12:57 ` [perfmon2] " stephane eranian
2010-01-18 13:06 ` Frederic Weisbecker
2010-01-18 12:53 ` stephane eranian
2010-01-18 13:00 ` 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=7c86c4471001180546v74ac3b16ia8c7cadf2a030204@mail.gmail.com \
--to=eranian@googlemail.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--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;
as well as URLs for NNTP newsgroup(s).