From: Qian Cai <quic_qiancai@quicinc.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
<linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"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>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [GIT PULL] scheduler updates for v5.18
Date: Mon, 21 Mar 2022 09:13:22 -0400 [thread overview]
Message-ID: <Yjh58h8cpcPERVZA@qian> (raw)
In-Reply-To: <YjhZUezhnamHAl0H@gmail.com>
On Mon, Mar 21, 2022 at 11:54:09AM +0100, Ingo Molnar wrote:
> Huang Ying (3):
> sched/numa-balancing: Move some document to make it consistent with the code
> sched/numa: Fix NUMA topology for systems with CPU-less nodes
> sched/numa: Avoid migrating task to CPU-less node
Linus, I don't think you want to merge this as-is. This will introduce a
kernel crash on arm64 NUMA as mentioned in this thread,
https://lore.kernel.org/lkml/Yh6H8SPSqpjv1dl7@qian
Ying sent an updated patch to fix the crash but is missing from this pull
request for some reasons.
https://lore.kernel.org/lkml/87y21lkxlv.fsf_-_@yhuang6-desk2.ccr.corp.intel.com/
next prev parent reply other threads:[~2022-03-21 13:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:54 [GIT PULL] scheduler updates for v5.18 Ingo Molnar
2022-03-21 13:13 ` Qian Cai [this message]
2022-03-21 23:59 ` Huang, Ying
2022-03-22 0:18 ` Linus Torvalds
2022-03-22 0:54 ` Huang, Ying
2022-03-22 1:08 ` Linus Torvalds
2022-03-22 7:35 ` Ingo Molnar
2022-03-22 7:48 ` Ingo Molnar
2022-03-22 8:18 ` Huang, Ying
2022-03-22 11:07 ` Ingo Molnar
2022-03-21 15:44 ` Nathan Chancellor
2022-03-22 7:54 ` Ingo Molnar
2022-03-22 15:32 ` Nathan Chancellor
2022-03-22 15:39 ` Randy Dunlap
2022-03-22 11:10 ` [GIT PULL -v2] " Ingo Molnar
2022-03-22 23:27 ` pr-tracker-bot
2022-03-22 23:27 ` [GIT PULL] " pr-tracker-bot
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=Yjh58h8cpcPERVZA@qian \
--to=quic_qiancai@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=ying.huang@intel.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