Messages in this thread | | | Date | Thu, 3 Sep 2015 21:04:11 +0200 | From | Jiri Olsa <> | Subject | Re: [tip:perf/urgent] perf evlist: Open event on evsel cpus and threads |
| |
On Thu, Sep 03, 2015 at 09:38:16PM +0300, Adrian Hunter wrote:
SNIP
> > > >perf_evlist__propagate_maps is called from perf_evlist__create_maps, > >so if evsel is added later it will not be affected, perhaps we need > >something like below > > Yes but it would be nice to have a single function to do it that knows > the rules for when the evsel->cpus should be retained. Say: > int __perf_evlist__propagate_maps(struct perf_evlist *evlist, struct perf_evsel *evsel) > then call it from perf_evlist__propagate_maps(), perf_evlist__add() and > perf_evlist__splice_list_tail(). Probably need to add a member to perf_evlist > to know when the evlist->cpus should replace the evsel->cpus
ook,
jirka
| |