From: Qing Wong <wangqing7171@gmail.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Qing Wang <wangqing7171@gmail.com>
Subject: [PATCH 0/2] perf/core: Fix broken throttling bugs
Date: Sat, 5 Apr 2025 22:16:33 +0800 [thread overview]
Message-ID: <20250405141635.243786-1-wangqing7171@gmail.com> (raw)
From: Qing Wang <wangqing7171@gmail.com>
There is a bug that broken throttling, this patchset intends
to improve the accuracy of throttling.
This patchset does two changes:
- Revert a specific patch to avoid broken throttling when
max_samples_per_tick>1.
- Add throttling judgement when max_samples_per_tick=1.
base-commit: acc4d5ff0b61
Qing Wang (2):
Revert "perf/core: Fix hardlockup failure caused by perf throttle"
perf/core: Fix broken throttling when max_samples_per_tick=1
kernel/events/core.c | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-05 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 14:16 Qing Wong [this message]
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
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=20250405141635.243786-1-wangqing7171@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 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.