The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: soolaugust@gmail.com
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: "zhidao su (Xiaomi)" <soolaugust@gmail.com>,
	mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
	kprateek.nayak@amd.com, jstultz@google.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: align proxy wakeup buddy handling with EEVDF
Date: Mon,  6 Jul 2026 17:08:12 +0800	[thread overview]
Message-ID: <20260706090812.3469388-1-soolaugust@gmail.com> (raw)
In-Reply-To: <CAKfTPtAQGgAQsy=RMQSg=q025spJHgQObmBcMroAQt0uo7h4Xw@mail.gmail.com>

From: "zhidao su (Xiaomi)" <soolaugust@gmail.com>

On Mon, Jul 06, 2026 at 10:16:47AM +0200, Vincent Guittot wrote:
> Which version are you using ? there is nothing like
> check_preempt_wakeup_fair() in mainline or tip/sched/core
>
> And does the issue still apply with the latest scheduler changes?

Thanks for checking, and sorry for the noise.

You are right. I based this on an old local proxy-exec work branch and
failed to state the base tree/commit in the submission. That branch still
had check_preempt_wakeup_fair(), but current mainline/tip and the newer
proxy-exec branches have moved to wakeup_preempt_fair().

I rechecked the newer code and the wakeup path has already been reworked
around preempt_action/set_preempt_buddy(), including the
PREEMPT_WAKEUP_SHORT buddy cleanup path. So this patch does not apply to
the current scheduler code and should be ignored.

I'll fix my local pre-send checks so patches like this have to apply to
the intended target baseline before I send them.

Thanks,
zhidao

      reply	other threads:[~2026-07-06  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  2:34 [PATCH] sched/fair: align proxy wakeup buddy handling with EEVDF zhidao su (Xiaomi)
2026-07-06  8:16 ` Vincent Guittot
2026-07-06  9:08   ` soolaugust [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=20260706090812.3469388-1-soolaugust@gmail.com \
    --to=soolaugust@gmail.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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