From: Thomas Richter <tmricht@linux.ibm.com>
To: linux-s390@vger.kernel.org
Cc: Thomas Richter <tmricht@linux.ibm.com>
Subject: [PATCH 0/3 v5] Add CPU hotplug support for PAI PMU
Date: Mon, 24 Aug 2026 15:17:48 +0200 [thread overview]
Message-ID: <20260824131751.179275-1-tmricht@linux.ibm.com> (raw)
V5: Add findings from Sashiko
- Add cpus_read_lock() and cpus_read_unlock() in patch 3.
V4: Add findings from Sumanth and updated patch 3/3.
- Fix reference count for CPU hotplug remove while multiple
per-task events are active.
V3: Add findings from Sumanth and updated patch 3/3.
- Refined Fixes: commit id and messages
- Handle cpuhp_setup_state() failure
V2: Add findings from Sumanth and updated patch 3/3.
- handle possible NULL pointer dereference in pai_event_destroy_cpu()
- handle possibe memory allocation failure in pai_online_cpu()
- add Reviewed-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
to patch 1/3 and patch 2/3.
Add support for CPU hotplug add and remove for PAI PMU.
Patch 1: Change function argument list
Patch 2: Move locking from CPU scope to event scope
Patch 3: Add CPU hotplug handler
Thomas Richter (3):
s390/pai: Use PAI PMU index as parameter replacing event
s390/pai: Move locking to event init and delete
s390/pai: Support CPU hotplug for PMU PAI
arch/s390/include/asm/pai.h | 1 -
arch/s390/kernel/perf_pai.c | 186 +++++++++++++++++++++++++-----------
2 files changed, 132 insertions(+), 55 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-24 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 13:17 Thomas Richter [this message]
2026-08-24 13:17 ` [PATCH 1/3] s390/pai: Use PAI PMU index as parameter replacing event Thomas Richter
2026-08-24 13:26 ` sashiko-bot
2026-08-24 13:17 ` [PATCH 2/3] s390/pai: Move locking to event init and delete Thomas Richter
2026-08-24 13:29 ` sashiko-bot
2026-08-24 13:17 ` [PATCH 3/3 v5] s390/pai: Support CPU hotplug for PMU PAI Thomas Richter
2026-08-24 13:27 ` sashiko-bot
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=20260824131751.179275-1-tmricht@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=linux-s390@vger.kernel.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