Prev: [PATCH] firewire: core: integrate software-forced bus resets with bus management
Next: 2.6.35-rc* regression: ERROR: Unable to locate IOAPIC for GSI *
From: Christoph Hellwig on 8 Jul 2010 14:00
On Thu, Jul 08, 2010 at 07:48:08PM +0200, Peter Zijlstra wrote:
> On Thu, 2010-07-08 at 13:35 -0400, Christoph Hellwig wrote:
>
> > What kind of infrastructure is perf using for recording
> > mmap()/mremap()/brk() information?
>
> A direct hook into mmap_region(), see perf_event_mmap().
>
> We used to only track VM_EXEC regions, but these days we can also track
> data regions (although it wouldn't track mremap and brk I think).
>
> We need the VM_EXEC maps to make sense of the instruction pointer
> samples.
>
> Eric recently added support for !VM_EXEC mmap() in order to interpret
> linear addresses provided by things like the software pagefault events
> and certain powerpc hardware events.

Maybe the user reporting should use trace points everywhere, leaving
the direct hook just for the executable tracking?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: [PATCH] firewire: core: integrate software-forced bus resets with bus management
Next: 2.6.35-rc* regression: ERROR: Unable to locate IOAPIC for GSI *