[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150908065713.GB29167@krava.brq.redhat.com>
Date: Tue, 8 Sep 2015 08:57:13 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Adrian Hunter <adrian.hunter@...el.com>
Cc: Arnaldo Carvalho de Melo <acme@...hat.com>, mingo@...nel.org,
kan.liang@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 00/14] perf tools: Fix gaps propagating maps
On Mon, Sep 07, 2015 at 05:27:42PM +0300, Adrian Hunter wrote:
> Hi
>
> Here is V2 of "Fix gaps propagating maps" that fixes some problems
> revealed by to d988d5ee6478 ("perf evlist: Open event on evsel cpus and threads")
>
> Changes in V2:
> Split into multiple patches
> Add evsel->own_cpus to identify evsels with their own cpu map
> And consequently don't need to unpropagate
>
> perf tools: Fix perf_evlist__splice_list_tail not setting evlist
> New patch
>
> perf tools: Fix task exit test setting maps
> New patch
>
> perf tools: Fix software clock events test setting maps
> New patch
>
>
> Adrian Hunter (14):
> perf tools: Simplify perf_evlist__propagate_maps logic
> perf tools: Simplify perf_evlist__set_maps logic
> perf tools: Remove redundant validation from perf_evlist__propagate_maps
> perf tools: Add evlist->has_user_cpus
> perf tools: Fix perf_evlist__splice_list_tail not setting evlist
> perf tools: Fix missing thread_map__put in perf_evlist__propagate_maps
> perf tools: Add evsel->own_cpus
> perf tools: Make perf_evlist__set_maps() more resilient
> perf tools: Make perf_evlist__create_maps() use perf_evlist__set_maps()
> perf tools: Factor out a function to propagate maps for a single evsel
> perf tools: Fix perf_evlist__add() not propagating maps
> perf tools: Fix perf_evlist__create_syswide_maps() not propagating maps
> perf tools: Fix task exit test setting maps
> perf tools: Fix software clock events test setting maps
other than my 2 comments, I'm ok with this patchset, nice! ;-)
thanks,
jirka
--
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