Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1312327
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC] perf record: missing buildid for callstack modules |
| Date | 2016-01-19 16:30 +0100 |
| Message-ID | <qSGoi-1fW-13@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <qPOBI-5zs-11@gated-at.bofh.it> <qQ4Gu-8a9-15@gated-at.bofh.it> <qQ87o-28L-15@gated-at.bofh.it> <qQqnE-6iI-5@gated-at.bofh.it> <qSFVg-Oo-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Jan 19, 2016 at 11:56:40PM +0900, Namhyung Kim wrote: > > But but ... why is #2 a problem with mtime? If we have an out of date record in > > the perf.data, then the perf.data is uninteresting in 99% of the usecases! It's > > out of date, most likely because the binary the developer is working on got > > rebuilt, or the system got upgraded - in both cases the developer does not care > > about the old records anymore... > > We have 'perf diff' command which compares old and new performance > results of a same program. People can use it to see how much improved > in the new version than the baseline. In this case, the old binary > should be found from the old perf.data. Just means they'll have to use perf-archive or whatnot before that works. Making the regular perf-record dead slow just so that a few more complex workloads work doesn't make sense.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC] perf record: missing buildid for callstack modules Namhyung Kim <namhyung@kernel.org> - 2016-01-19 16:00 +0100
Re: [RFC] perf record: missing buildid for callstack modules Peter Zijlstra <peterz@infradead.org> - 2016-01-19 16:30 +0100
Re: [RFC] perf record: missing buildid for callstack modules Arnaldo Carvalho de Melo <acme@kernel.org> - 2016-01-19 16:50 +0100
csiph-web