Sched_ext development
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: sashiko-bot@kernel.org, sched-ext@lists.linux.dev,
	Andrea Righi <arighi@nvidia.com>
Subject: Re: [PATCH v4 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when the donor changes during dispatch
Date: Sat, 31 Oct 2026 07:12:32 -1000	[thread overview]
Message-ID: <3a0b7df208af30eb77c18104c6df156a@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-192051@kernel.org>

Hello,

On Sat, Oct 31, 2026 at 04:55:55PM +0000, sashiko-bot@kernel.org wrote:
> - [Medium] sched_ext: dispatch_one() emits ops.cpu_acquire() before checking stale prev

ops.cpu_acquire() is deprecated, so this doesn't matter.

Thanks.

--
tejun

  reply	other threads:[~2026-10-31 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 16:28 [PATCH v4 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when the donor changes during dispatch Tejun Heo
2026-10-31 16:55 ` sashiko-bot
2026-10-31 17:12   ` Tejun Heo [this message]
2026-11-01  6:55 ` Andrea Righi
2026-11-02  6:35 ` Tejun Heo

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=3a0b7df208af30eb77c18104c6df156a@kernel.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sched-ext@lists.linux.dev \
    /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