[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37D7C6CF3E00A74B8858931C1DB2F077015C6EDB@SHSMSX103.ccr.corp.intel.com>
Date: Thu, 11 Sep 2014 13:50:50 +0000
From: "Liang, Kan" <kan.liang@...el.com>
To: Jiri Olsa <jolsa@...hat.com>
CC: "acme@...nel.org" <acme@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"ak@...ux.intel.com" <ak@...ux.intel.com>
Subject: RE: [PATCH V5 2/3] perf tools: parse the pmu event prefix and surfix
> On Wed, Sep 10, 2014 at 01:55:31PM -0400, kan.liang@...el.com wrote:
>
> SNIP
>
> > + struct perf_pmu_event_symbol *pmu2 =
> > + (struct perf_pmu_event_symbol *) p2;
> > +
> > + return strcmp(pmu1->symbol, pmu2->symbol); }
> > +
> > +/*
> > + * Read the pmu events list from sysfs
> > + * Save it into perf_pmu_events_list
> > + */
> > +static void perf_pmu__parse_init(void) {
> > +
> > + struct perf_pmu *pmu = NULL;
> > + struct perf_pmu_alias *alias;
> > + int len = 0;
> > +
> > + while ((pmu = perf_pmu__scan(pmu)) != NULL)
> > + list_for_each_entry(alias, &pmu->aliases, list) {
> > + if (!strcmp(pmu->name, "cpu")) {
> > + if (strchr(alias->name, '-'))
> > + len++;
> > + len++;
> > + }
> > + }
> > + if (len == 0)
> > + return;
>
> s oif 'len' is 0 we will scan all the time? maybe we want some separate 'init'
> variable..
>
Maybe we can reuse the "perf_pmu_events_list_num".
static int perf_pmu_events_list_num;
If len is 0, we just set perf_pmu_events_list_num to -1.
Is it OK?
Thanks,
Kan
--
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