From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/6] perf: Add interface to add general events to sysfs
Date: Tue, 19 Jul 2011 15:52:06 +0800 [thread overview]
Message-ID: <1311061926.3938.205.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <1310996068.13765.67.camel@twins>
On Mon, 2011-07-18 at 21:34 +0800, Peter Zijlstra wrote:
> On Fri, 2011-07-15 at 14:34 +0000, Lin Ming wrote:
> > PMU can implement ::add_events() to add its general events to sysfs.
> >
> > For example,
> >
> > /sys/bus/event_source/devices/uncore/events
> > └── cycle
> >
> > Signed-off-by: Lin Ming <ming.m.lin@intel.com>
> > ---
> > include/linux/perf_event.h | 9 +++++++
> > kernel/events/core.c | 52 ++++++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 61 insertions(+), 0 deletions(-)
> >
> > diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> > index 3f2711c..14337a3 100644
> > --- a/include/linux/perf_event.h
> > +++ b/include/linux/perf_event.h
> > @@ -676,6 +676,14 @@ struct pmu {
> > * for each successful ->add() during the transaction.
> > */
> > void (*cancel_txn) (struct pmu *pmu); /* optional */
> > +
> > + void (*add_events) (void);
> > +};
>
> I'd rather not have a function pointer here, and all the kobj thingies
> can be hooking into the existing struct device, right?
I forgot to mention one important reason why I added a function pointer.
The events can only be added to sysfs after PMU sysfs is initialized in
perf_event_sysfs_init ->
pmu_dev_alloc
> @@ -5571,6 +5571,8 @@ static int pmu_dev_alloc(struct pmu *pmu)
> if (ret)
> goto free_dev;
>
> + if (pmu->add_events)
> + pmu->add_events();
So we need a pmu callback which is called in pmu_dev_alloc to add events
to sysfs.
You suggested a new interface,
int perf_pmu_add_event(struct pmu *pmu, const char *name, u64 config)
But where should it be called?
I guess you mean to call it in pmu init function, for example,
uncore_pmu_init.
But pmu init function maybe called before perf_event_sysfs_init, which
means the pmu sysfs has not been initialized yet.
Lin Ming
next prev parent reply other threads:[~2011-07-19 7:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 14:34 [PATCH v2 0/6] perf: Intel uncore pmu counting support Lin Ming
2011-07-15 14:34 ` [PATCH v2 1/6] perf: Add interface to add general events to sysfs Lin Ming
2011-07-18 13:34 ` Peter Zijlstra
2011-07-18 14:00 ` Lin Ming
2011-07-19 7:52 ` Lin Ming [this message]
2011-07-25 7:08 ` Lin Ming
2011-07-25 7:57 ` Peter Zijlstra
2011-07-25 8:32 ` Lin Ming
2011-07-25 8:11 ` Lin Ming
2011-07-25 8:32 ` Peter Zijlstra
2011-07-25 15:20 ` Greg KH
2011-07-26 1:06 ` Lin Ming
2011-07-26 4:42 ` Greg KH
2011-07-26 5:50 ` Lin Ming
2011-07-15 14:34 ` [PATCH v2 2/6] perf, x86: Add Intel Nehalem/Westmere uncore pmu Lin Ming
2011-07-15 14:48 ` Lin Ming
2011-07-18 14:20 ` Peter Zijlstra
2011-07-18 14:54 ` Lin Ming
2011-07-18 16:11 ` Peter Zijlstra
2011-07-15 14:35 ` [PATCH v2 3/6] perf, x86: Add Intel SandyBridge " Lin Ming
2011-07-15 14:35 ` [PATCH v2 4/6] perf: Remove perf_event_attr::type check Lin Ming
2011-07-15 14:35 ` [PATCH v2 5/6] perf tool: Allow system-wide 'perf stat' without 'command' Lin Ming
2011-07-15 14:35 ` [PATCH v2 6/6] perf tool: Parse general/raw events from sysfs Lin Ming
2011-08-06 20:10 ` Stephane Eranian
2011-08-06 23:38 ` Lin Ming
2011-08-07 23:47 ` Stephane Eranian
2011-08-08 1:08 ` Lin Ming
2011-08-08 5:54 ` Stephane Eranian
2011-08-08 8:48 ` Peter Zijlstra
2011-08-08 8:57 ` Lin Ming
2011-08-08 9:03 ` Peter Zijlstra
2011-08-11 22:38 ` Stephane Eranian
2011-08-15 19:18 ` Corey Ashford
2011-08-31 12:21 ` [PATCH v2 0/6] perf: Intel uncore pmu counting support 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=1311061926.3938.205.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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