From: Jinchao Wang <wangjinchao600@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
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>,
"Liang, Kan" <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jinchao Wang <wangjinchao600@gmail.com>
Subject: [PATCH] perf/HWBP: Optimize __modify_bp_slot() handling
Date: Tue, 2 Sep 2025 17:17:54 +0800 [thread overview]
Message-ID: <20250902091759.590664-1-wangjinchao600@gmail.com> (raw)
Skip unnecessary release/reserve when old and new types share the same
slot.
Reserve the new slot first, then release the old one to maintain
consistency and avoid transient failures.
Signed-off-by: Jinchao Wang <wangjinchao600@gmail.com>
---
kernel/events/hw_breakpoint.c | 23 ++++++++++-------------
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/kernel/events/hw_breakpoint.c b/kernel/events/hw_breakpoint.c
index 8ec2cb688903..1cc9cb32ceb4 100644
--- a/kernel/events/hw_breakpoint.c
+++ b/kernel/events/hw_breakpoint.c
@@ -625,23 +625,20 @@ void release_bp_slot(struct perf_event *bp)
static int __modify_bp_slot(struct perf_event *bp, u64 old_type, u64 new_type)
{
int err;
+ enum bp_type_idx old_type_idx, new_type_idx;
- __release_bp_slot(bp, old_type);
+ old_type_idx = find_slot_idx(old_type);
+ new_type_idx = find_slot_idx(new_type);
+ if (old_type_idx == new_type_idx)
+ return 0;
err = __reserve_bp_slot(bp, new_type);
- if (err) {
- /*
- * Reserve the old_type slot back in case
- * there's no space for the new type.
- *
- * This must succeed, because we just released
- * the old_type slot in the __release_bp_slot
- * call above. If not, something is broken.
- */
- WARN_ON(__reserve_bp_slot(bp, old_type));
- }
+ if (err)
+ return err;
- return err;
+ __release_bp_slot(bp, old_type);
+
+ return 0;
}
static int modify_bp_slot(struct perf_event *bp, u64 old_type, u64 new_type)
--
2.43.0
reply other threads:[~2025-09-02 9:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250902091759.590664-1-wangjinchao600@gmail.com \
--to=wangjinchao600@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
all inboxes | Powered by JetHome®