linux-kernel - Re: [PATCH v7 14/23] sched: Handle blocked-waiter migration (and return migration)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANDhNCqaxrtLy70Q_sdFzWV7nt+3yG512my8hLA2DoHJ+ZywZw@mail.gmail.com>
Date: Thu, 4 Jan 2024 15:33:05 -0800
From: John Stultz <jstultz@...gle.com>
To: Phil Auld <pauld@...hat.com>
Cc: Metin Kaya <metin.kaya@....com>, LKML <linux-kernel@...r.kernel.org>, 
	Joel Fernandes <joelaf@...gle.com>, Qais Yousef <qyousef@...gle.com>, Ingo Molnar <mingo@...hat.com>, 
	Peter Zijlstra <peterz@...radead.org>, Juri Lelli <juri.lelli@...hat.com>, 
	Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>, 
	Valentin Schneider <vschneid@...hat.com>, Steven Rostedt <rostedt@...dmis.org>, 
	Ben Segall <bsegall@...gle.com>, Zimuzo Ezeozue <zezeozue@...gle.com>, 
	Youssef Esmat <youssefesmat@...gle.com>, Mel Gorman <mgorman@...e.de>, 
	Daniel Bristot de Oliveira <bristot@...hat.com>, Will Deacon <will@...nel.org>, Waiman Long <longman@...hat.com>, 
	Boqun Feng <boqun.feng@...il.com>, "Paul E. McKenney" <paulmck@...nel.org>, 
	Xuewen Yan <xuewen.yan94@...il.com>, K Prateek Nayak <kprateek.nayak@....com>, 
	Thomas Gleixner <tglx@...utronix.de>, kernel-team@...roid.com
Subject: Re: [PATCH v7 14/23] sched: Handle blocked-waiter migration (and
 return migration)

On Tue, Jan 2, 2024 at 7:34 AM Phil Auld <pauld@...hat.com> wrote:
>
> On Thu, Dec 21, 2023 at 04:12:57PM +0000 Metin Kaya wrote:
> > On 20/12/2023 12:18 am, John Stultz wrote:
> > > Add logic to handle migrating a blocked waiter to a remote
> > > cpu where the lock owner is runnable.
> > >
> > > Additionally, as the blocked task may not be able to run
> > > on the remote cpu, add logic to handle return migration once
> > > the waiting task is given the mutex.
> > >
> > > Because tasks may get migrated to where they cannot run,
> > > this patch also modifies the scheduling classes to avoid
> > > sched class migrations on mutex blocked tasks, leaving
> > > proxy() to do the migrations and return migrations.
> >
> > s/proxy/find_proxy_task/
> >
>
> While fixing that paragraph, probably:
>
> s/this patch also modifies/also modify/

Fixed as well. Thanks!
-john