From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf parse-events: Fix parsing of >30kb event strings
Date: Sat, 4 Oct 2025 09:58:36 -0300 [thread overview]
Message-ID: <aOEZ_HOcIMggsebi@x1> (raw)
In-Reply-To: <CAP-5=fUOpiJypozewCSi6Avg2pQnjmvNcFMM5iUsbTR1P_47zQ@mail.gmail.com>
On Fri, Oct 03, 2025 at 02:25:39PM -0700, Ian Rogers wrote:
> On Wed, Sep 17, 2025 at 11:05 AM Ian Rogers <irogers@google.com> wrote:
> > On Thu, Sep 4, 2025 at 9:26 PM Ian Rogers <irogers@google.com> wrote:
> > > Whilst cleaning up "%option reject" make the header files accurately
> > > reflect functions used in the code and tidy up not requiring yywrap.
> > > Measuring on the "PMU JSON event tests" a modest reduction of 0.41%
> > > user time and 0.27% max resident size was observed. More importantly
> > > this change fixes parsing large metrics and event strings.
> > Ping. I think this may have gotten lost in noise about things like
> > hardware json and the python metrics. It is a small change, bug fix
> > and performance win. It can land independently of anything else. PTAL.
> It'd be nice to land this for the v6.18 pull. I don't think it has any
> visible implications and just makes stuff better.
Applied and now testing on the container build set.
- Arnaldo
prev parent reply other threads:[~2025-10-04 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 4:26 [PATCH v1] perf parse-events: Fix parsing of >30kb event strings Ian Rogers
2025-09-17 18:05 ` Ian Rogers
2025-10-03 21:25 ` Ian Rogers
2025-10-04 12:58 ` Arnaldo Carvalho de Melo [this message]
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=aOEZ_HOcIMggsebi@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.