From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Ian Rogers <irogers@google.com>,
Namhyung Kim <namhyung@kernel.org>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, Zecheng Li <zli94@ncsu.edu>
Subject: Re: [PATCH] perf annotate: Fix register usage in data type profiling
Date: Fri, 6 Feb 2026 18:19:41 -0300 [thread overview]
Message-ID: <aYZa7Z32z_WlQrsh@x1> (raw)
In-Reply-To: <qncykxscahgsit26ctsja4jox4353uburbfoehfcuneycbgnvg@jvgs3twjn2rq>
On Fri, Feb 06, 2026 at 10:08:55AM +0100, Dmitry Dolgov wrote:
> > On Thu, Feb 05, 2026 at 09:00:43PM -0800, Ian Rogers wrote:
> > It'd be nice to have a test on this to avoid a regression. Dmitrii's patch:
> > https://lore.kernel.org/linux-perf-users/20260127083030.5909-1-9erthalion6@gmail.com/
> > does that for a Rust struct Buf, but it'd be nice to do something similar for C.
> Agree, and I was planning to extend the tests in the patch above with a
> C workload as well.
Hey, did you test the patch? Having a Tested-by you in addition to the
Reported-by would be nice.
- Arnaldo
next prev parent reply other threads:[~2026-02-06 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 1:27 [PATCH] perf annotate: Fix register usage in data type profiling Namhyung Kim
2026-02-06 5:00 ` Ian Rogers
2026-02-06 9:08 ` Dmitry Dolgov
2026-02-06 21:19 ` Arnaldo Carvalho de Melo [this message]
2026-02-08 12:24 ` Dmitry Dolgov
2026-02-06 21:18 ` 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=aYZa7Z32z_WlQrsh@x1 \
--to=acme@kernel.org \
--cc=9erthalion6@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zli94@ncsu.edu \
/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