[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aOVxlEXDMKJyIhME@x1>
Date: Tue, 7 Oct 2025 17:01:24 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: James Clark <james.clark@...aro.org>
Cc: Ian Rogers <irogers@...gle.com>, Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>, Leo Yan <leo.yan@....com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf tests: Don't retest sections in "Object code
reading"
On Tue, Oct 07, 2025 at 10:10:12AM +0100, James Clark wrote:
> On 06/10/2025 4:21 pm, Ian Rogers wrote:
> > On Mon, Oct 6, 2025 at 6:11 AM James Clark <james.clark@...aro.org> wrote:
> > > + data = zalloc(sizeof(*data));
> > > + if (!data)
> > > + return true;
> > > + data->addr = addr;
> > > + strlcpy(data->path, path, sizeof(data->path));
> > nit: perhaps strdup rather than having 4kb per tested_section.
> Oh yeah that would have been better, not sure why I didn't do it that way.
> Although the max sections I saw was around 50, and it's usually a lot less
> so it's probably not worth the churn to change it now that Arnaldo's applied
> it?
I see you submitted a patch for using strdup() and then there is a need
for checking the strdup(), etc.
Since at this point this is an improvement on a test and all is sitting
in linux-next and the window is closing for v6.18, lets leave this for
the next window, ok?
These would be good things for some tool to catch, before it gets sent,
but that is another rabbit hole :-)
Thanks,
- Arnaldo
Powered by blists - more mailing lists