Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934495Ab2J3U3T (ORCPT ); Tue, 30 Oct 2012 16:29:19 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:40326 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934354Ab2J3U3S (ORCPT ); Tue, 30 Oct 2012 16:29:18 -0400 MIME-Version: 1.0 Date: Tue, 30 Oct 2012 21:29:16 +0100 Message-ID: Subject: [BUG] perf tools: does not process data mmaps correctly From: Stephane Eranian To: LKML Cc: Arnaldo Carvalho de Melo , Namhyung Kim , Peter Zijlstra , "mingo@elte.hu" , "ak@linux.intel.com" Content-Type: text/plain; charset=UTF-8 X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1338 Lines: 40 Arnaldo, A long time ago, I brought up the issue of perf failing to resolve data symbols despite having the MAP__VARIABLE map type. Now that I have posted the PEBS-LL patch series, there is a test case to debug this. I looked again at it today. Start from ip__resolve_data() in my patchset. IT is looking for a data symbol given an address. Seems to me the core of the problem is how perf processes the MMAP records in machine__process_mmap_event(): int machine__process_mmap_event(struct machine *machine, union perf_event *event) { ... thread = machine__findnew_thread(machine, event->mmap.pid); if (thread == NULL) goto out_problem; map = map__new(&machine->user_dsos, event->mmap.start, event->mmap.len, event->mmap.pgoff, event->mmap.pid, event->mmap.filename, MAP__FUNCTION); I don't see any effort to distinguish code from data here. All mmaps are treated as code. That could be fine, if then you drop MAP__VARIABLE. So how is this supposed to work? Thanks. -- 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/