From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V3 0/1] perf tools: Allow config terms with breakpoints
Date: Tue, 6 Jun 2023 08:00:33 +0300 [thread overview]
Message-ID: <afe1c05a-2b77-c3d8-aacf-b4c7bebb8bf8@intel.com> (raw)
In-Reply-To: <20230525082902.25332-1-adrian.hunter@intel.com>
On 25/05/23 11:29, Adrian Hunter wrote:
> Hi
>
> Here is a patch (V3) to the event parser for breakpoint events.
> I am not that familiar with flex / bison, but it seemed to
> need trailing context to stop the mem event colon and slash
> delimiters from getting mixed up with delimiters for config
> terms or event modifiers. Please look closely at that.
>
>
> Changes in V3:
>
> Add Ian's Reviewed-by
> Re-base
Still applies. Any more comments?
>
> Changes in V2:
>
> Add comments to tools/perf/util/parse-events.l
> Add a test for 2 mem events back to back with config terms
>
>
> Adrian Hunter (1):
> perf tools: Allow config terms with breakpoints
>
> tools/perf/tests/parse-events.c | 157 ++++++++++++++++++++++++++++++++++++++++
> tools/perf/util/parse-events.c | 23 +++++-
> tools/perf/util/parse-events.h | 6 +-
> tools/perf/util/parse-events.l | 23 +++++-
> tools/perf/util/parse-events.y | 42 ++++++-----
> 5 files changed, 224 insertions(+), 27 deletions(-)
>
>
> Regards
> Adrian
next prev parent reply other threads:[~2023-06-06 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 8:29 [PATCH V3 0/1] perf tools: Allow config terms with breakpoints Adrian Hunter
2023-05-25 8:29 ` [PATCH V3 1/1] " Adrian Hunter
2023-06-06 5:00 ` Adrian Hunter [this message]
2023-06-06 18:15 ` [PATCH V3 0/1] " Arnaldo Carvalho de Melo
2023-06-06 19:22 ` Arnaldo Carvalho de Melo
2023-06-06 19:37 ` Adrian Hunter
2023-06-07 5:33 ` Adrian Hunter
2023-06-07 13:48 ` Arnaldo Carvalho de Melo
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=afe1c05a-2b77-c3d8-aacf-b4c7bebb8bf8@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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).