mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Joel Fernandes <joelagnelf@nvidia.com>,
	Qais Yousef <qyousef@layalina.io>, Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>,
	Zimuzo Ezeozue <zezeozue@google.com>,
	Mel Gorman <mgorman@suse.de>, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Metin Kaya <Metin.Kaya@arm.com>,
	Xuewen Yan <xuewen.yan94@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Suleiman Souhlal <suleiman@google.com>,
	kuyo chang <kuyo.chang@mediatek.com>, hupu <hupu.gm@gmail.com>,
	kernel-team@android.com
Subject: Re: [RESEND][PATCH v18 6/8] sched: Add an initial sketch of the find_proxy_task() function
Date: Fri, 11 Jul 2025 15:30:03 +0200	[thread overview]
Message-ID: <20250711133003.GH905792@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CANDhNCoMvY0s0AyePNouWqxdRpXCYJE=28E_b8RdmJ_2px_OBA@mail.gmail.com>

On Thu, Jul 10, 2025 at 05:43:36PM -0700, John Stultz wrote:

> > > @@ -6648,6 +6652,89 @@ static bool try_to_block_task(struct rq *rq, struct task_struct *p,
> > >       return true;
> > >  }
> > >
> > > +#ifdef CONFIG_SCHED_PROXY_EXEC
> > > +static inline struct task_struct *proxy_resched_idle(struct rq *rq)
> > > +{
> > > +     put_prev_set_next_task(rq, rq->donor, rq->idle);
> > > +     rq_set_donor(rq, rq->idle);
> > > +     set_tsk_need_resched(rq->idle);
> > > +     return rq->idle;
> > > +}
> >
> > Nothing cares about the return value.
> 
> Well, nothing in this patch, but the last patch in this series I sent
> here uses it.  But if you think it makes the series easier to grok and
> I can drop it here and add the return in that later patch.

I found it in the later patch; I meant to reply here, but promptly
forgot. It can stay here I suppose, no harm done.

  reply	other threads:[~2025-07-11 13:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 20:43 [RESEND][PATCH v18 0/8] Single RunQueue Proxy Execution (v18) John Stultz
2025-07-07 20:43 ` [RESEND][PATCH v18 1/8] sched: Add CONFIG_SCHED_PROXY_EXEC & boot argument to enable/disable John Stultz
2025-07-07 20:43 ` [RESEND][PATCH v18 2/8] locking/mutex: Rework task_struct::blocked_on John Stultz
2025-07-07 20:43 ` [RESEND][PATCH v18 3/8] locking/mutex: Add p->blocked_on wrappers for correctness checks John Stultz
2025-07-08  6:43   ` K Prateek Nayak
2025-07-09  4:50     ` John Stultz
2025-07-07 20:43 ` [RESEND][PATCH v18 4/8] sched: Move update_curr_task logic into update_curr_se John Stultz
2025-07-07 20:43 ` [RESEND][PATCH v18 5/8] sched: Fix runtime accounting w/ split exec & sched contexts John Stultz
2025-07-10  9:45   ` Peter Zijlstra
2025-07-10 17:25     ` John Stultz
2025-07-11 13:28       ` Peter Zijlstra
2025-07-07 20:43 ` [RESEND][PATCH v18 6/8] sched: Add an initial sketch of the find_proxy_task() function John Stultz
2025-07-10 10:02   ` Peter Zijlstra
2025-07-11  0:43     ` John Stultz
2025-07-11 13:30       ` Peter Zijlstra [this message]
2025-07-12  3:58       ` John Stultz
2025-07-07 20:43 ` [RESEND][PATCH v18 7/8] sched: Fix proxy/current (push,pull)ability John Stultz
2025-07-07 20:43 ` [RESEND][PATCH v18 8/8] sched: Start blocked_on chain processing in find_proxy_task() John Stultz

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=20250711133003.GH905792@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Metin.Kaya@arm.com \
    --cc=boqun.feng@gmail.com \
    --cc=bsegall@google.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=hupu.gm@gmail.com \
    --cc=joelagnelf@nvidia.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kernel-team@android.com \
    --cc=kprateek.nayak@amd.com \
    --cc=kuyo.chang@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=qyousef@layalina.io \
    --cc=rostedt@goodmis.org \
    --cc=suleiman@google.com \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=will@kernel.org \
    --cc=xuewen.yan94@gmail.com \
    --cc=zezeozue@google.com \
    /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®