From: Peter Zijlstra <peterz@infradead.org>
To: Seiji Nishikawa <snishika@redhat.com>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Josh Don <joshdon@google.com>,
linux-kernel@vger.kernel.org,
syzbot+681e729b2cf0d4860042@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com,
Ahmed Abdelraoof <araoof@amazon.de>
Subject: Re: [PATCH RESEND] sched/core: Do not touch SMT siblings that have not joined the core yet
Date: Thu, 5 Nov 2026 16:09:22 +0100 [thread overview]
Message-ID: <20261105150922.GR1813469@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20261105134035.170438-1-snishika@redhat.com>
On Thu, Nov 05, 2026 at 10:40:35PM +0900, Seiji Nishikawa wrote:
> On Thu, Nov 05, 2026 at 11:10:18AM +0100, Peter Zijlstra wrote:
> > Of the two, I like your better for being more consistent -- but you're
> > doing the same thing 4 times, which does beg the question if we cannot
> > wrap that nicer.
> >
> > How about so then?
>
> Thanks, this looks nicer.
>
> I tested it on v7.4-rc1 with the syzbot C reproducer. The warning did
> not trigger in about 1250 seconds (about 6100 offline/online cycles of
> CPU 1).
>
> Should I send a v2 with this change, or will you apply it yourself?
I have it; if only 0-day would hurry up with the current batch of
sched/urgent patches :/
next prev parent reply other threads:[~2026-11-05 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 2:20 [PATCH RESEND] sched/core: Do not touch SMT siblings that have not joined the core yet Seiji Nishikawa
2026-11-04 9:34 ` Peter Zijlstra
2026-11-04 18:16 ` Seiji Nishikawa
2026-11-05 10:10 ` Peter Zijlstra
2026-11-05 13:40 ` Seiji Nishikawa
2026-11-05 15:09 ` Peter Zijlstra [this message]
2026-11-09 8:38 ` [tip: sched/urgent] " tip-bot2 for Seiji Nishikawa
2026-11-09 9:28 ` [tip: sched/core] " tip-bot2 for Seiji Nishikawa
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=20261105150922.GR1813469@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=araoof@amazon.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joshdon@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=rostedt@goodmis.org \
--cc=snishika@redhat.com \
--cc=syzbot+681e729b2cf0d4860042@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.