Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759000Ab0FPOxA (ORCPT ); Wed, 16 Jun 2010 10:53:00 -0400 Received: from casper.infradead.org ([85.118.1.10]:38248 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756024Ab0FPOw7 convert rfc822-to-8bit (ORCPT ); Wed, 16 Jun 2010 10:52:59 -0400 Subject: Re: [RFC] perf/perf_events: misleading number of samples due to mmap() From: Peter Zijlstra To: Stephane Eranian Cc: Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, mingo@elte.hu, paulus@samba.org, davem@davemloft.net, fweisbec@gmail.com, perfmon2-devel@lists.sf.net, eranian@gmail.com In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Wed, 16 Jun 2010 16:52:42 +0200 Message-ID: <1276699962.1745.599.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 632 Lines: 12 On Wed, 2010-06-16 at 16:40 +0200, Stephane Eranian wrote: > This leads me to another point. For per-thread sampling, why > do we need to record mmap() events happening *outside* of > the process? I can understand the exception of kernel modules. How does that happen? The per-thread events should be on the per-task context, so another task's mmap() events should never end up there. -- 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/