[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140417113221.GA7422@krava.brq.redhat.com>
Date: Thu, 17 Apr 2014 13:32:21 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Christian Borntraeger <borntraeger@...ibm.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
KVM <kvm@...r.kernel.org>,
linux-s390 <linux-s390@...r.kernel.org>,
Cornelia Huck <cornelia.huck@...ibm.com>,
linux-kernel@...r.kernel.org,
Alexander Yarygin <yarygin@...ux.vnet.ibm.com>
Subject: Re: [PATCH] perf/tool: Fix usage of trace events with '-' in trace
system name.
On Tue, Mar 25, 2014 at 11:15:29AM +0100, Paolo Bonzini wrote:
> Il 24/03/2014 21:49, Christian Borntraeger ha scritto:
> > event_legacy_tracepoint:
> >+PE_NAME '-' PE_NAME ':' PE_NAME
> >+{
> >+ struct parse_events_evlist *data = _data;
> >+ struct list_head *list;
> >+ char sys_name[strlen($1) + strlen($3) + 2];
> >+ sprintf(&sys_name, "%s-%s", $1, $3);
> >+
> >+ ALLOC_LIST(list);
> >+ ABORT_ON(parse_events_add_tracepoint(list, &data->idx, &sys_name, $5));
> >+ $$ = list;
> >+}
>
> Why isn't '-' part of PE_NAME?
hi Paolo ;-)
because it screws cache events parsing.. we need some code factoring
in this part
Acked-by: Jiri Olsa <jolsa@...hat.com>
it'd be nice to add test to tests/parse-events.c, probably s390 specific,
because the parsing code touches the tracepoint format file
thanks,
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists