From: Dominique Martinet <asmadeus@codewreck.org>
To: Jiri Olsa <olsajiri@gmail.com>, Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] perf parse: Allow names to start with digits
Date: Mon, 10 Oct 2022 14:38:54 +0900 [thread overview]
Message-ID: <Y0Ov7hSuWQJlYAdW@codewreck.org> (raw)
In-Reply-To: <CAP-5=fXgNTW1eXRZhz-s_AfP+v1Oyx1zdksm-Q0B4YVPAgjKxw@mail.gmail.com> <YsLOKEqzp0Syz/Rt@krava>
Hi Jiri, Ian,
Jiri Olsa wrote on Mon, Jul 04, 2022 at 01:25:28PM +0200:
> > If you're ok with that I can resend this as three patches: my original
> > patch, a patch with your diff and test_event() keeping current
> > behaviour, and a last patch adding that last flag and testing 9p without
> > format check.
> >
> > (and if you don't think it's worth checking probe existence same thing
> > but even simpler)
>
> I have that patch split into 2 separated changes,
> I'll try to send it later today
It's been a while (I had totally forgotten), but I don't think I saw
this patch.
For reminder you've requested that I add some test for a tracepoint
starting with digits e.g. 9p:9p_client_res but there's nothing commonly
available to use there, so you added a way to only check without
checking if a backing tracepoint exist, but I see no trace of the update
you sent here:
https://lore.kernel.org/all/YsGduWiTvkM2/tHv@krava/
Should I take it, do the split you suggested and send it together with a
resend of my original patch and new test?
Ian Rogers wrote on Mon, Jul 04, 2022 at 02:39:05PM -0700:
> > diff --git a/tools/perf/util/parse-events.l b/tools/perf/util/parse-events.l
> > index 5b6e4b5249cf..4133d6950d29 100644
> > --- a/tools/perf/util/parse-events.l
> > +++ b/tools/perf/util/parse-events.l
> > @@ -211,7 +211,7 @@ bpf_source [^,{}]+\.c[a-zA-Z0-9._]*
> > num_dec [0-9]+
> > num_hex 0x[a-fA-F0-9]+
> > num_raw_hex [a-fA-F0-9]+
> > -name [a-zA-Z_*?\[\]][a-zA-Z0-9_*?.\[\]!]*
> > +name [a-zA-Z0-9_*?\[\]][a-zA-Z0-9_*?.\[\]!]*
>
> Perhaps this would be cleaner as:
> name [a-zA-Z0-9_*?\[\]!]+
> except that would allow a name to start with an exclamation. Would
> that be an issue?
Sorry for the lack of reply -- I have no opinion on this as long as we
can use digits.
I can't imagine any probe starting with . or !, but that does not seem
to create any ambiguity with the rest of the grammar that I can see
either so I think it'd be fine, but I'm not comfortable deciding.
Thanks,
--
Dominique
next prev parent reply other threads:[~2022-10-10 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 6:15 [PATCH] perf parse: Allow names to start with digits Dominique Martinet
2022-07-02 9:49 ` Dominique Martinet
2022-07-02 12:24 ` Arnaldo Carvalho de Melo
2022-07-02 15:48 ` Jiri Olsa
2022-07-02 23:51 ` Dominique Martinet
2022-07-03 13:46 ` Jiri Olsa
2022-07-03 23:58 ` Dominique Martinet
2022-07-04 11:25 ` Jiri Olsa
2022-10-10 5:38 ` Dominique Martinet [this message]
2022-10-10 14:05 ` Jiri Olsa
2022-07-04 21:39 ` Ian Rogers
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=Y0Ov7hSuWQJlYAdW@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).