include/linux/sched/topology.h | 3 ++ kernel/sched/core.c | 3 ++ kernel/sched/fair.c | 74 +++++++++++++++++++++++----------- kernel/sched/features.h | 5 +++ kernel/sched/sched.h | 7 ++++ kernel/sched/topology.c | 6 +++ 6 files changed, 75 insertions(+), 23 deletions(-)
This series is to backport following patches for v6.12: link: https://lore.kernel.org/lkml/20251107160645.929564468@infradead.org/ Peter Zijlstra (3): sched/fair: Revert max_newidle_lb_cost bump sched/fair: Small cleanup to sched_balance_newidle() sched/fair: Small cleanup to update_newidle_cost() sched/fair: Proportional newidle balance include/linux/sched/topology.h | 3 ++ kernel/sched/core.c | 3 ++ kernel/sched/fair.c | 74 +++++++++++++++++++++++----------- kernel/sched/features.h | 5 +++ kernel/sched/sched.h | 7 ++++ kernel/sched/topology.c | 6 +++ 6 files changed, 75 insertions(+), 23 deletions(-) -- 2.40.4
Greg, following upstream patches will directly apply to v6.17, so I am not sending for v6.17: https://github.com/torvalds/linux/commit/d206fbad9328ddb68ebabd7cf7413392acd38081.patch https://github.com/torvalds/linux/commit/e78e70dbf603c1425f15f32b455ca148c932f6c1.patch https://github.com/torvalds/linux/commit/08d473dd8718e4a4d698b1113a14a40ad64a909b.patch https://github.com/torvalds/linux/commit/33cf66d88306663d16e4759e9d24766b0aaa2e17.patch -Ajay On Wed, Dec 3, 2025 at 5:08 PM Ajay Kaher <ajay.kaher@broadcom.com> wrote: > > This series is to backport following patches for v6.12: > link: https://lore.kernel.org/lkml/20251107160645.929564468@infradead.org/ > > Peter Zijlstra (3): > sched/fair: Revert max_newidle_lb_cost bump > sched/fair: Small cleanup to sched_balance_newidle() > sched/fair: Small cleanup to update_newidle_cost() > sched/fair: Proportional newidle balance > > include/linux/sched/topology.h | 3 ++ > kernel/sched/core.c | 3 ++ > kernel/sched/fair.c | 74 +++++++++++++++++++++++----------- > kernel/sched/features.h | 5 +++ > kernel/sched/sched.h | 7 ++++ > kernel/sched/topology.c | 6 +++ > 6 files changed, 75 insertions(+), 23 deletions(-) > > -- > 2.40.4 >
On Wed, Dec 03, 2025 at 05:23:05PM +0530, Ajay Kaher wrote: > Greg, following upstream patches will directly apply to v6.17, so I am > not sending for v6.17: > > https://github.com/torvalds/linux/commit/d206fbad9328ddb68ebabd7cf7413392acd38081.patch > https://github.com/torvalds/linux/commit/e78e70dbf603c1425f15f32b455ca148c932f6c1.patch > https://github.com/torvalds/linux/commit/08d473dd8718e4a4d698b1113a14a40ad64a909b.patch > https://github.com/torvalds/linux/commit/33cf66d88306663d16e4759e9d24766b0aaa2e17.patch Please don't use github for kernel stuff.... Anyway, these are not in a -rc kernel yet, so I really shouldn't be taking them unless the author/maintainer agrees they should go in "right now". And given that these weren't even marked as cc: stable in the first place, why the rush? Also, you forgot about 6.18.y, right? thanks, greg k-h
On Wed, Dec 3, 2025 at 6:46 PM Greg KH <gregkh@linuxfoundation.org> wrote: > > On Wed, Dec 03, 2025 at 05:23:05PM +0530, Ajay Kaher wrote: > > Greg, following upstream patches will directly apply to v6.17, so I am > > not sending for v6.17: > > > > https://github.com/torvalds/linux/commit/d206fbad9328ddb68ebabd7cf7413392acd38081.patch > > https://github.com/torvalds/linux/commit/e78e70dbf603c1425f15f32b455ca148c932f6c1.patch > > https://github.com/torvalds/linux/commit/08d473dd8718e4a4d698b1113a14a40ad64a909b.patch > > https://github.com/torvalds/linux/commit/33cf66d88306663d16e4759e9d24766b0aaa2e17.patch > > Please don't use github for kernel stuff.... ok. > Anyway, these are not in a -rc kernel yet, so I really shouldn't be > taking them unless the author/maintainer agrees they should go in > "right now". And given that these weren't even marked as cc: stable in > the first place, why the rush? Agree. No rush. > Also, you forgot about 6.18.y, right? Yes. However, upstream patches will directly apply till v6.17. -Ajay
On Thu, Dec 04, 2025 at 10:36:02AM +0530, Ajay Kaher wrote: > On Wed, Dec 3, 2025 at 6:46 PM Greg KH <gregkh@linuxfoundation.org> wrote: > > > > On Wed, Dec 03, 2025 at 05:23:05PM +0530, Ajay Kaher wrote: > > > Greg, following upstream patches will directly apply to v6.17, so I am > > > not sending for v6.17: > > > > > > https://github.com/torvalds/linux/commit/d206fbad9328ddb68ebabd7cf7413392acd38081.patch > > > https://github.com/torvalds/linux/commit/e78e70dbf603c1425f15f32b455ca148c932f6c1.patch > > > https://github.com/torvalds/linux/commit/08d473dd8718e4a4d698b1113a14a40ad64a909b.patch > > > https://github.com/torvalds/linux/commit/33cf66d88306663d16e4759e9d24766b0aaa2e17.patch > > > > Please don't use github for kernel stuff.... > > ok. > > > Anyway, these are not in a -rc kernel yet, so I really shouldn't be > > taking them unless the author/maintainer agrees they should go in > > "right now". And given that these weren't even marked as cc: stable in > > the first place, why the rush? > > Agree. No rush. > > > Also, you forgot about 6.18.y, right? > > Yes. However, upstream patches will directly apply till v6.17. Sorry for the delay, now queued up. greg k-h
© 2016 - 2026 Red Hat, Inc.