From: Jiri Olsa <jolsa@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-kernel@vger.kernel.org,
Alexander Yarygin <yarygin@linux.vnet.ibm.com>
Subject: Re: [PATCH] perf/tool: Fix usage of trace events with '-' in trace system name.
Date: Thu, 17 Apr 2014 13:32:21 +0200 [thread overview]
Message-ID: <20140417113221.GA7422@krava.brq.redhat.com> (raw)
In-Reply-To: <53315741.9010508@redhat.com>
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@redhat.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
next prev parent reply other threads:[~2014-04-17 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 20:49 Christian Borntraeger
2014-03-25 10:15 ` Paolo Bonzini
2014-04-17 11:32 ` Jiri Olsa [this message]
2014-04-17 11:41 ` Christian Borntraeger
2014-04-17 11:45 ` Jiri Olsa
2014-04-21 15:43 ` Alexander Yarygin
2014-04-23 11:45 ` Jiri Olsa
2014-04-23 12:34 ` Christian Borntraeger
2014-04-17 14:40 ` Jiri Olsa
2014-04-23 11:12 ` Christian Borntraeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140417113221.GA7422@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=yarygin@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome