Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1301560
| From | Jiri Olsa <jolsa@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 6/6] perf record: Always store data mmaps |
| Date | 2016-01-05 15:20 +0100 |
| Message-ID | <qNACT-3VY-25@gated-at.bofh.it> (permalink) |
| References | <qGNlw-4hK-3@gated-at.bofh.it> <qGNlw-4hK-5@gated-at.bofh.it> <qNxOG-1jL-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Jan 05, 2016 at 08:16:34PM +0900, Namhyung Kim wrote: > On Thu, Dec 17, 2015 at 09:26:55PM +0100, Jiri Olsa wrote: > > Currently we don't synthesize data mmap by default. It depends > > on -d option, that enables data address sampling. > > > > But we've seen cases (softice) where DWARF unwinder went through > > non executable mmaps, which we need to lookup in MAP__VARIABLE tree. > > > > Given the discussion we had with Arnaldo, where he mentioned > > he wanted to unify MAP__VARIABLE/MAP__FUNCTION anyway, I'm > > making data mmaps to be synthesized unconditionally. > > But I'm afraid of increased data size. Could you check how much is it? I'll check jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 6/6] perf record: Always store data mmaps Namhyung Kim <namhyung@kernel.org> - 2016-01-05 12:20 +0100 Re: [PATCH 6/6] perf record: Always store data mmaps Jiri Olsa <jolsa@redhat.com> - 2016-01-05 15:20 +0100
csiph-web