From: Tim Chen <tim.c.chen@linux.intel.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Tim Chen <tim.c.chen@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Libo Chen <libo.chen@oracle.com>,
Abel Wu <wuyun.abel@bytedance.com>,
Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org, Chen Yu <yu.c.chen@intel.com>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
Zhao Liu <zhao1.liu@intel.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>
Subject: Re: [PATCH 0/2] Fix NUMA sched domain build errors for GNR-X and CWF-X
Date: Mon, 25 Aug 2025 14:38:42 -0700 [thread overview]
Message-ID: <23c06fbda6e18354eaf253abb6b106292b69bdde.camel@linux.intel.com> (raw)
In-Reply-To: <b69fd9da-7b98-4df8-9446-2fe6a717f50f@amd.com>
On Mon, 2025-08-25 at 09:48 +0530, K Prateek Nayak wrote:
> Hello Tim,
>
> On 8/23/2025 1:44 AM, Tim Chen wrote:
> > While testing Granite Rapids X (GNR-X) and Clearwater Forest X (CWF-X) in
> > SNc-3 mode, we encountered sched domain build errors reported in dmesg.
> > Asymmetric node distances from local node to to nodes in remote package
> > was not expected by the scheduler domain code and also led to excessive
> > number of sched domain hierachy levels.
> >
> > Fix the missing NUMA domain level set in topology_span_sane() check and
> > also simplify the distance to nodes in remote package to retain distance
> > symmetry and make the NUMA topology sane for GNR-X and CWF-X.
>
> I did some sanity testing on an EPYC platform on NPS2/4 and didn't
> see any changes to the sched domain layout or the sched_node_distance()
> being used when constructing them with the series.
>
> Feel free to include:
>
> Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
>
Thanks for testing it.
Tim
prev parent reply other threads:[~2025-08-25 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 20:14 [PATCH 0/2] Fix NUMA sched domain build errors for GNR-X and CWF-X Tim Chen
2025-08-22 20:14 ` [PATCH 1/2] sched: topology: Fix topology validation error Tim Chen
2025-08-25 3:18 ` K Prateek Nayak
2025-08-25 7:58 ` Peter Zijlstra
2025-08-25 9:23 ` Peter Zijlstra
2025-08-25 7:25 ` Peter Zijlstra
2025-08-25 21:09 ` Tim Chen
2025-08-22 20:14 ` [PATCH 2/2] sched: Fix sched domain build error for GNR-X, CWF-X in SNC-3 mode Tim Chen
2025-08-25 5:08 ` Chen, Yu C
2025-08-25 7:56 ` Peter Zijlstra
2025-08-25 21:36 ` Tim Chen
2025-08-25 20:05 ` Tim Chen
2025-08-25 4:18 ` [PATCH 0/2] Fix NUMA sched domain build errors for GNR-X and CWF-X K Prateek Nayak
2025-08-25 21:38 ` Tim Chen [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=23c06fbda6e18354eaf253abb6b106292b69bdde.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=len.brown@intel.com \
--cc=libo.chen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tim.c.chen@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vinicius.gomes@intel.com \
--cc=vschneid@redhat.com \
--cc=wuyun.abel@bytedance.com \
--cc=yu.c.chen@intel.com \
--cc=zhao1.liu@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 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.