Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753948Ab2J2JoA (ORCPT ); Mon, 29 Oct 2012 05:44:00 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:53168 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751701Ab2J2Jn7 (ORCPT ); Mon, 29 Oct 2012 05:43:59 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 29 Oct 2012 10:43:57 +0100 Message-ID: Subject: Re: [BUG] perf parser: does not support arbitrary new sysfs events From: Stephane Eranian To: Andi Kleen Cc: LKML , Jiri Olsa , Peter Zijlstra , "mingo@elte.hu" , Namhyung Kim 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: 1183 Lines: 31 On Mon, Oct 29, 2012 at 2:50 AM, Andi Kleen wrote: > Stephane Eranian writes: > >> Hi, >> >> The latest round of perf parser changes broke my PEBS-LL patch series >> (at the last minute). For PEBS-LL, I need to add to generic events but I want >> to keep them PMU specific. As such, they need to live in the sysfs events >> subdir: /sys/devices/cpu/events/mem-loads, sys/devices/cpu/events/mem-stores. >> >> Given your latest rounds of sysfs event changes, I had to modify my kernel >> patches to fit those two new events within your perf_pmu_events_attr tables. >> >> But now, when I try to do: >> >> $ perf record -e cpu/mem-loads/ .... > > - is not supported in an event name. I fixed this in my patchkit > Yes, this was indeed the problem. Glad you tracked it down. We need this patch ASAP. > Yes the sysfs stuff in general is quite fragile. > I would say complicated rather than fragile. -- 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/