From: Peter Zijlstra <peterz@infradead.org>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
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>,
Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org, Chen Yu <yu.c.chen@intel.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
Zhao Liu <zhao1.liu@intel.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Arjan Van De Ven <arjan.van.de.ven@intel.com>
Subject: Re: [PATCH v5 0/2] Fix NUMA sched domain build errors for GNR and CWF
Date: Mon, 6 Oct 2025 21:34:21 +0200 [thread overview]
Message-ID: <20251006193421.GA3245006@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <cover.1759515405.git.tim.c.chen@linux.intel.com>
On Fri, Oct 03, 2025 at 12:31:26PM -0700, Tim Chen wrote:
> Tim Chen (2):
> sched: Create architecture specific sched domain distances
> sched/topology: Fix sched domain build error for GNR, CWF in SNC-3
> mode
>
> arch/x86/kernel/smpboot.c | 70 +++++++++++++++++++++
> include/linux/sched/topology.h | 1 +
> kernel/sched/topology.c | 108 ++++++++++++++++++++++++++-------
> 3 files changed, 157 insertions(+), 22 deletions(-)
Right, I suppose this'll do. I'll throw it on the pile for post -rc1 or
so.
prev parent reply other threads:[~2025-10-06 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 19:31 Tim Chen
2025-10-03 19:31 ` [PATCH v5 1/2] sched: Create architecture specific sched domain distances Tim Chen
2025-10-03 19:31 ` [PATCH v5 2/2] sched/topology: Fix sched domain build error for GNR, CWF in SNC-3 mode Tim Chen
2025-10-06 19:34 ` Peter Zijlstra [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=20251006193421.GA3245006@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arjan.van.de.ven@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=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=tim.c.chen@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vinicius.gomes@intel.com \
--cc=vschneid@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®