From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Leo Yan <leo.yan@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Mike Leach <mike.leach@linaro.org>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Al Grant <al.grant@arm.com>
Subject: Re: [PATCH v2 2/2] perf c2c: Update documentation for adding memory event table
Date: Tue, 20 Jan 2026 17:32:04 -0300 [thread overview]
Message-ID: <aW_mRD7W7QkAE3Lw@x1> (raw)
In-Reply-To: <651e1a79-356f-4f86-a6c3-8119f1c6c98f@linaro.org>
On Mon, Dec 15, 2025 at 10:40:04AM +0200, James Clark wrote:
> On 12/12/2025 19:25, Leo Yan wrote:
> > Users may occasionally need to see which options are applied to memory
> > events. This helps to understand the behavior of "perf c2c" and
> > "perf mem", and provides guidance for configuring memory event options
> > directly.
> >
> > Add a table to track memory events and their corresponding options, and
> > include the Arm SPE events in it.
> >
> > Suggested-by: Al Grant <al.grant@arm.com>
> > Signed-off-by: Leo Yan <leo.yan@arm.com>
>
> Reviewed-by: James Clark <james.clark@linaro.org>
Thanks, applied to perf-tools-next,
- Arnaldo
next prev parent reply other threads:[~2026-01-20 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 17:24 [PATCH v2 0/2] perf arm_spe: Minor event configs housekeeping Leo Yan
2025-12-12 17:24 ` [PATCH v2 1/2] perf mem: Simplify Arm SPE event config Leo Yan
2025-12-12 17:25 ` [PATCH v2 2/2] perf c2c: Update documentation for adding memory event table Leo Yan
2025-12-15 8:40 ` James Clark
2026-01-20 20:32 ` Arnaldo Carvalho de Melo [this message]
2026-01-16 11:09 ` [PATCH v2 0/2] perf arm_spe: Minor event configs housekeeping Leo Yan
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=aW_mRD7W7QkAE3Lw@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=al.grant@arm.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=will@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