Em Thu, Oct 17, 2013 at 07:32:15PM +0200, Stephane Eranian escreveu: > > For now, we disable the extended MMAP record support (MMAP2). > We have identified cases where it would not report the correct > mapping information, clone(VM_CLONE) but with separate pids. > We will revisit the support once we find a solution for this case. > > The patch changes the kernel to return EINVAL if attr->mmap2 > is set. The patch also modifies the perf tool to use regular PERF_RECORD_MMAP > for synthetic events and it also prevents the tool from requesting attr->mmap2 > mode because the kernel would reject it. > > The support will be revisited once the kenrel interface is updated. > > In V2, we reduce the patch to the strict minimum. > In V3, we avoid calling perf_event_open() with mmap2 set because we > know it will fail and require fallback retry.
Again it applied, but with some fuzz, which branch did you coded this against? Testing... [acme@zoo linux]$ patch -p1 < /wb/1 patching file kernel/events/core.c Hunk #1 succeeded at 6767 (offset -6 lines). patching file tools/perf/util/event.c patching file tools/perf/util/evsel.c Hunk #1 succeeded at 678 with fuzz 1. [acme@zoo linux]$ - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/