From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.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>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Caleb Biggers" <caleb.biggers@intel.com>,
"Weilin Wang" <weilin.wang@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Perry Taylor" <perry.taylor@intel.com>,
"Thomas Falcon" <thomas.falcon@intel.com>
Subject: Re: [PATCH v5 00/16] Intel TPEBS min/max/mean/last support
Date: Wed, 23 Apr 2025 10:33:20 -0300 [thread overview]
Message-ID: <aAjsIGKS6e3MfI60@x1> (raw)
In-Reply-To: <CAP-5=fVo_yGgEwndavWaNAQRg=1MR121PQ-KwOW0HsUWGBLLnA@mail.gmail.com>
On Mon, Apr 21, 2025 at 11:13:49AM -0700, Ian Rogers wrote:
> On Mon, Apr 14, 2025 at 12:08 PM Liang, Kan <kan.liang@linux.intel.com> wrote:
> > On 2025-04-14 1:41 p.m., Ian Rogers wrote:
> > > Ian Rogers (16):
> > > perf intel-tpebs: Cleanup header
> > > perf intel-tpebs: Simplify tpebs_cmd
> > > perf intel-tpebs: Rename tpebs_start to evsel__tpebs_open
> > > perf intel-tpebs: Separate evsel__tpebs_prepare out of
> > > evsel__tpebs_open
> > > perf intel-tpebs: Move cpumap_buf out of evsel__tpebs_open
> > > perf intel-tpebs: Reduce scope of tpebs_events_size
> > > perf intel-tpebs: Inline get_perf_record_args
> > > perf intel-tpebs: Ensure events are opened, factor out finding
> > > perf intel-tpebs: Refactor tpebs_results list
> > > perf intel-tpebs: Add support for updating counts in evsel__tpebs_read
> > > perf intel-tpebs: Add mutex for tpebs_results
> > > perf intel-tpebs: Don't close record on read
> > > perf intel-tpebs: Use stats for retirement latency statistics
> > > perf stat: Add mean, min, max and last --tpebs-mode options
> > > perf pmu-events: Add retirement latency to JSON events inside of perf
> > > perf record: Retirement latency cleanup in evsel__config
> > Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
> Ping.
> It would be great if we could land:
> https://lore.kernel.org/lkml/CAP-5=fWxuKHLZJjd2NVWjA7ktCX6X3yQBsH2kh+eTTaNcSqbTg@mail.gmail.com/T/#m1bba00c3a699397b54e1a77da9b9ff392b435e4d
> and then land this series.
Applied that and then this one,
Thanks,
- Arnaldo
prev parent reply other threads:[~2025-04-23 13:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 17:41 [PATCH v5 00/16] Intel TPEBS min/max/mean/last support Ian Rogers
2025-04-14 17:41 ` [PATCH v5 01/16] perf intel-tpebs: Cleanup header Ian Rogers
2025-04-14 17:41 ` [PATCH v5 02/16] perf intel-tpebs: Simplify tpebs_cmd Ian Rogers
2025-04-14 17:41 ` [PATCH v5 03/16] perf intel-tpebs: Rename tpebs_start to evsel__tpebs_open Ian Rogers
2025-04-14 17:41 ` [PATCH v5 04/16] perf intel-tpebs: Separate evsel__tpebs_prepare out of evsel__tpebs_open Ian Rogers
2025-04-14 17:41 ` [PATCH v5 05/16] perf intel-tpebs: Move cpumap_buf " Ian Rogers
2025-04-14 17:41 ` [PATCH v5 06/16] perf intel-tpebs: Reduce scope of tpebs_events_size Ian Rogers
2025-04-14 17:41 ` [PATCH v5 07/16] perf intel-tpebs: Inline get_perf_record_args Ian Rogers
2025-04-14 17:41 ` [PATCH v5 08/16] perf intel-tpebs: Ensure events are opened, factor out finding Ian Rogers
2025-04-14 17:41 ` [PATCH v5 09/16] perf intel-tpebs: Refactor tpebs_results list Ian Rogers
2025-04-23 14:23 ` Arnaldo Carvalho de Melo
2025-04-23 15:04 ` Ian Rogers
2025-04-14 17:41 ` [PATCH v5 10/16] perf intel-tpebs: Add support for updating counts in evsel__tpebs_read Ian Rogers
2025-04-14 17:41 ` [PATCH v5 11/16] perf intel-tpebs: Add mutex for tpebs_results Ian Rogers
2025-04-14 17:41 ` [PATCH v5 12/16] perf intel-tpebs: Don't close record on read Ian Rogers
2025-04-14 17:41 ` [PATCH v5 13/16] perf intel-tpebs: Use stats for retirement latency statistics Ian Rogers
2025-04-14 17:41 ` [PATCH v5 14/16] perf stat: Add mean, min, max and last --tpebs-mode options Ian Rogers
2025-04-23 13:56 ` Arnaldo Carvalho de Melo
2025-04-23 15:03 ` Ian Rogers
2025-04-14 17:41 ` [PATCH v5 15/16] perf pmu-events: Add retirement latency to JSON events inside of perf Ian Rogers
2025-04-14 17:41 ` [PATCH v5 16/16] perf record: Retirement latency cleanup in evsel__config Ian Rogers
2025-04-14 19:08 ` [PATCH v5 00/16] Intel TPEBS min/max/mean/last support Liang, Kan
2025-04-21 18:13 ` Ian Rogers
2025-04-23 13:33 ` 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=aAjsIGKS6e3MfI60@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=caleb.biggers@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=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--cc=weilin.wang@intel.com \
/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