[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191014194619.GS9933@tassilo.jf.intel.com>
Date: Mon, 14 Oct 2019 12:46:19 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Jiri Olsa <jolsa@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Michael Petlan <mpetlan@...hat.com>
Subject: Re: [PATCH 3/3] perf tools: Make 'struct map_shared' truly shared
> > We may need a COW operation for this (hopefully rare) case.
>
> so the jitted mmaps are inserted into the data file
> and processed during report where they can overload
> existing maps - thats detected before addition in:
>
> thread__insert_map
> map_groups__fixup_overlappings
> - which uses COW way -> map__clone(map, false);
> to create new map
>
> other fixups to maps are being done only for kernel maps,
> where we dont have a problem, because there's only one copy
I assume the same is true for /tmp/perf-* processing?
Thanks for looking into it.
-Andi
Powered by blists - more mailing lists