Em Fri, Sep 05, 2014 at 09:09:49AM +0900, Namhyung Kim escreveu: > >> Before: > >> $ perf record -a usleep 1
> >> $ perf buildid-list > >> 00d5ff078efe1d30b8492854f259215fd877ce30 > >> /lib/modules/3.16.0-rc2+/build/vmlinux > >> 78186287bba77069a056a5ccbeb14b7fd2ca3a4b /usr/lib64/libc-2.17.so > >> $ perf buildid-list -H > >> 0000000000000000000000000000000000000000 [kernel.kallsyms] > >> 78186287bba77069a056a5ccbeb14b7fd2ca3a4b /usr/lib64/libc-2.17.so > >> After: > >> $ perf record -a usleep 1 > >> $ perf buildid-list > >> 00d5ff078efe1d30b8492854f259215fd877ce30 [kernel.kallsyms] > > We are losing information, namely the pathname for the kernel used, that > > may be useful in analysis. > Right. That's a problem. > > Why not make sure that if there is a build-id in the perf.data header, > > then we completely refusing anything that doesn't match the build-id? > > I.e. the name is irrelevant for this purpose, the contents, as keyed by > > the build-id, is what matters. > The perf report rebuilds machine states from the event records only. In > this case, the kernel map was recorded in the name of [kernel.kallsyms] > so it couldn't find the build-id from the table. Ok, but then we can special case this one, no? Somehow mark in the buildid table that that entry is the one for the kernel and hook it up to the synthesized event that has the [kernel.kallsyms].ref_reloc_sym entry. - 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/
