From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Zhaoyang Li <lizy04@hust.edu.cn>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING
Date: Wed, 21 May 2025 22:03:50 -0400 [thread overview]
Message-ID: <20250521145353-5e9f6a84b5aa803f@stable.kernel.org> (raw)
In-Reply-To: <20250521020216.539748-1-lizy04@hust.edu.cn>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 53dac345395c0d2493cbc2f4c85fe38aef5b63f5
WARNING: Author mismatch between patch and upstream commit:
Backport author: Zhaoyang Li<lizy04@hust.edu.cn>
Commit author: Frederic Weisbecker<frederic@kernel.org>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (different SHA1: e456a88bddae)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 53dac345395c0 ! 1: d4b970537740a hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING
@@ Metadata
## Commit message ##
hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING
+ [ Upstream commit 53dac345395c0d2493cbc2f4c85fe38aef5b63f5 ]
+
hrtimers are migrated away from the dying CPU to any online target at
the CPUHP_AP_HRTIMERS_DYING stage in order not to delay bandwidth timers
handling tasks involved in the CPU hotplug forward progress.
@@ Commit message
Link: https://lore.kernel.org/all/20250117232433.24027-1-frederic@kernel.org
Closes: 20241213203739.1519801-1-usamaarif642@gmail.com
- ## include/linux/hrtimer_defs.h ##
-@@ include/linux/hrtimer_defs.h: struct hrtimer_cpu_base {
+ Signed-off-by: Zhaoyang Li <lizy04@hust.edu.cn>
+
+ ## include/linux/hrtimer.h ##
+@@ include/linux/hrtimer.h: struct hrtimer_cpu_base {
ktime_t softirq_expires_next;
struct hrtimer *softirq_next_timer;
struct hrtimer_clock_base clock_base[HRTIMER_MAX_CLOCK_BASES];
+ call_single_data_t csd;
} ____cacheline_aligned;
-
+ static inline void hrtimer_set_expires(struct hrtimer *timer, ktime_t time)
## kernel/time/hrtimer.c ##
@@
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-05-22 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 15:01 FAILED: patch "[PATCH] hrtimers: Force migrate away hrtimers queued after" failed to apply to 6.1-stable tree gregkh
2025-05-13 6:04 ` [PATCH 6.1.y] hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING Zhaoyang Li
2025-05-13 18:49 ` Sasha Levin
2025-05-20 11:32 ` Greg KH
2025-05-20 13:21 ` 李朝阳
2025-05-21 2:02 ` Zhaoyang Li
2025-05-22 2:03 ` Sasha Levin [this message]
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=20250521145353-5e9f6a84b5aa803f@stable.kernel.org \
--to=sashal@kernel.org \
--cc=lizy04@hust.edu.cn \
--cc=stable@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