From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Falcon <thomas.falcon@intel.com>
Cc: 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>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [RESEND][PATCH v2 0/2] perf record: ratio-to-prev event term for auto counter reload
Date: Thu, 2 Oct 2025 16:35:51 -0300 [thread overview]
Message-ID: <aN7UF0MwmQnzk72W@x1> (raw)
In-Reply-To: <20250902164047.64261-1-thomas.falcon@intel.com>
On Tue, Sep 02, 2025 at 11:40:44AM -0500, Thomas Falcon wrote:
> The Auto Counter Reload (ACR)[1] feature is used to track the
> relative rates of two or more perf events, only sampling
> when a given threshold is exceeded. This helps reduce overhead
> and unnecessary samples. However, enabling this feature
> currently requires setting two parameters:
Can you please try to rebase to what is in tmp.perf-tools-next now?
- Arnaldo
next prev parent reply other threads:[~2025-10-02 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 16:40 [RESEND][PATCH v2 0/2] perf record: ratio-to-prev event term for auto counter reload Thomas Falcon
2025-09-02 16:40 ` [RESEND][PATCH v2 1/2] perf record: Add ratio-to-prev term Thomas Falcon
2025-09-24 21:34 ` Ian Rogers
2025-09-02 16:40 ` [RESEND][PATCH v2 2/2] perf record: Add auto counter reload parse and regression tests Thomas Falcon
2025-09-24 21:37 ` Ian Rogers
2025-09-24 19:09 ` [RESEND][PATCH v2 0/2] perf record: ratio-to-prev event term for auto counter reload Falcon, Thomas
2025-09-30 7:28 ` Mi, Dapeng
2025-10-02 15:38 ` Falcon, Thomas
2025-10-09 2:31 ` Mi, Dapeng
2025-10-02 19:35 ` Arnaldo Carvalho de Melo [this message]
2025-10-02 21:57 ` Falcon, Thomas
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=aN7UF0MwmQnzk72W@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.