Messages in this thread | | | Date | Tue, 30 Jul 2013 08:59:01 -0600 | From | David Ahern <> | Subject | Re: [PATCH 0/8] perf: add ability to sample physical data addresses |
| |
On 7/30/13 8:53 AM, Stephane Eranian wrote: > On Tue, Jul 30, 2013 at 4:50 PM, David Ahern <dsahern@gmail.com> wrote: >> On 7/30/13 8:21 AM, Stephane Eranian wrote: >>> >>> One thing that bothers me with the MMAP2 approach is that >>> it forces integration into perf. Now, you will need to analyze >>> the MMAP2 records. With my sample_type approach, you >>> simply needed a cmdline option on perf record, and then >>> you could dump the sample using perf report -D and feed >> >> >> what do you want that is not coming out via perf-script? >> > mmap records. Are they passed to scripts?
I don't do much with external scripts, but I do not believe they are passed. I use 'perf script -f <opts>' a lot to see the individual samples (e.g., tracepoints and software events).
It could easily be adapted to dump mmap events, but does not sound like it improves your workload.
David
| |