From: Qing Wang <wangqing7171@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, irogers@google.com,
jolsa@kernel.org, kan.liang@linux.intel.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mingo@redhat.com, namhyung@kernel.org
Subject: Re: [PATCH 2/2] perf/core: Fix broken throttling when max_samples_per_tick=1
Date: Fri, 18 Apr 2025 21:08:30 +0800 [thread overview]
Message-ID: <ca94f413-4e35-41fd-9554-c80d6e2707ac@gmail.com> (raw)
In-Reply-To: <20250418090302.GO38216@noisy.programming.kicks-ass.net>
Thank you very much for your review. Do you need me to reorganize the
patch and send it out? Because if only the second patch is accepted, its
context won't match the current mainline code.
On 4/18/2025 5:03 PM, Peter Zijlstra wrote:
> Fair enough I suppose. I'll make this apply without that revert -- it
> seems pointless to have that in between.
next prev parent reply other threads:[~2025-04-18 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 14:16 [PATCH 0/2] perf/core: Fix broken throttling bugs Qing Wong
2025-04-05 14:16 ` [PATCH 1/2] Revert "perf/core: Fix hardlockup failure caused by perf throttle" Qing Wong
2025-04-18 8:57 ` Peter Zijlstra
2025-04-05 14:16 ` [PATCH 2/2] perf/core: Fix broken throttling when max_samples_per_tick=1 Qing Wong
2025-04-18 9:03 ` Peter Zijlstra
2025-04-18 13:08 ` Qing Wang [this message]
2025-04-18 13:10 ` Peter Zijlstra
2025-04-18 13:19 ` Qing Wang
2025-04-30 11:58 ` [tip: perf/core] " tip-bot2 for Qing Wang
2025-04-15 14:22 ` [PATCH 0/2] perf/core: Fix broken throttling bugs Qing Wang
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=ca94f413-4e35-41fd-9554-c80d6e2707ac@gmail.com \
--to=wangqing7171@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@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 \
/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