From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Ian Rogers <irogers@google.com>,
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>,
Leo Yan <leo.yan@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tests: Don't retest sections in "Object code reading"
Date: Tue, 7 Oct 2025 17:01:24 -0300 [thread overview]
Message-ID: <aOVxlEXDMKJyIhME@x1> (raw)
In-Reply-To: <b39ffdd5-1692-46ed-86d9-726011c92036@linaro.org>
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@linaro.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
next prev parent reply other threads:[~2025-10-07 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 13:11 [PATCH] perf tests: Don't retest sections in "Object code reading" James Clark
2025-10-06 15:21 ` Ian Rogers
2025-10-06 20:03 ` Arnaldo Carvalho de Melo
2025-10-07 9:10 ` James Clark
2025-10-07 13:16 ` Ian Rogers
2025-10-07 20:01 ` Arnaldo Carvalho de Melo [this message]
2025-10-08 8:32 ` James Clark
2025-10-08 10:21 ` James Clark
2025-10-08 13:39 ` Dan Carpenter
2025-10-08 14:11 ` James Clark
2025-10-08 15:07 ` 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=aOVxlEXDMKJyIhME@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.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 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).