David Miller 4f8f382e63 perf tools: Don't clone maps from parent when synthesizing forks ... When synthesizing FORK events, we are trying to create thread objects for the already running tasks on the machine. Normally, for a kernel FORK event, we want to clone the parent's maps because that is what the kernel just did. But when synthesizing, this should not be done. If we do, we end up with overlapping maps as we process the sythesized MMAP2 events that get delivered shortly thereafter. Use the FORK event misc flags in an internal way to signal this situation, so we can elide the map clone when appropriate. Signed-off-by: David S. Miller <davem@davemloft.net> Cc: Don Zickus <dzickus@redhat.com> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Joe Mario <jmario@redhat.com> Link: http://lkml.kernel.org/r/20181030.222404.2085088822877051075.davem@davemloft.net [ Added comment about flag use in machine__process_fork_event(), use ternary op in thread__clone_map_groups() as suggested by Jiri ] Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>		2018-10-31 10:18:01 -03:00
..
asm	tools, perf: add and use optimized ring_buffer_{read_head, write_tail} helpers	2018-10-19 13:43:08 -07:00
asm-generic
linux	Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next	2018-10-24 06:47:44 +01:00
tools	tools: bpf: fix license for a compat header file	2018-09-19 23:49:58 +02:00
trace/events
uapi	perf tools: Don't clone maps from parent when synthesizing forks	2018-10-31 10:18:01 -03:00