[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100510122728.GB5563@nowhere>
Date: Mon, 10 May 2010 14:27:30 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Lin Ming <ming.m.lin@...el.com>, Ingo Molnar <mingo@...e.hu>,
"eranian@...il.com" <eranian@...il.com>,
"Gary.Mohr@...l.com" <Gary.Mohr@...l.com>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
Paul Mackerras <paulus@...ba.org>,
"David S. Miller" <davem@...emloft.net>,
Russell King <rmk+kernel@....linux.org.uk>,
Paul Mundt <lethal@...ux-sh.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH 2/9] perf: core, remove hw_perf_event_init
On Mon, May 10, 2010 at 12:19:29PM +0200, Peter Zijlstra wrote:
> On Mon, 2010-05-10 at 18:17 +0800, Lin Ming wrote:
> > On Mon, 2010-05-10 at 17:40 +0800, Peter Zijlstra wrote:
> > > On Mon, 2010-05-10 at 17:26 +0800, Lin Ming wrote:
> > > > +static struct pmu *perf_event_lookup_pmu(struct perf_event *event)
> > > > +{
> > > > + struct pmu *pmu;
> > > > + int pmu_id = event->attr.pmu_id;
> > > > +
> > > > + list_for_each_entry(pmu, &pmus, entry) {
> > > > + if (pmu->id == pmu_id)
> > > > + return pmu;
> > > > + }
> > > > +
> > > > + return NULL;
> > > > +}
> > >
> > > > +void perf_event_register_pmu(struct pmu *pmu)
> > > > +{
> > > > + pmu->id = pmu_id_curr++;
> > > > + list_add_tail(&pmu->entry, &pmus);
> > > > +}
> > >
> > > That will be wanting some sort of synchronization
> >
> > Will add a mutex to protect the list of pmus.
>
> I'm thinking RCU might be better suited, a mutex for lookup doesn't
> sound ideal.
Is it really needed? I expect this function to be called on boot
only.
In fact I would even suggest to tag it as __init.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists