From: Ionela Voinescu <ionela.voinescu@arm.com>
To: Yicong Yang <yangyicong@huawei.com>
Cc: yangyicong@hisilicon.com, sudeep.holla@arm.com,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, rafael@kernel.org, 21cnbao@gmail.com,
jonathan.cameron@huawei.com, linuxarm@huawei.com,
prime.zeng@huawei.com
Subject: Re: [PATCH] arch_topology: Make cluster topology span at least SMT CPUs
Date: Tue, 23 Aug 2022 18:53:23 +0100 [thread overview]
Message-ID: <YwUUEzULS1ha1rqY@arm.com> (raw)
In-Reply-To: <d0bc04af-5481-5df2-ff75-9072b4b047c1@huawei.com>
Hi,
On Tuesday 23 Aug 2022 at 21:05:47 (+0800), Yicong Yang wrote:
> On 2022/8/23 16:06, Ionela Voinescu wrote:
> > Hi Yicong,
> >
> > On Tuesday 23 Aug 2022 at 15:30:44 (+0800), Yicong Yang wrote:
> >> From: Yicong Yang <yangyicong@hisilicon.com>
> >>
> >> Currently cpu_clustergroup_mask() will return CPU mask if cluster span
> >> more or the same CPUs as cpu_coregroup_mask(). This will result topology
> >> borken on non-Cluster SMT machines.
> >
> > Might be worth adding here:.. "when building with CONFIG_SCHED_CLUSTER=y"
> >
>
> will add this qualifier. thanks.
>
> >>
> >
> > I thought I had covered this case, but I think I had considered LLC
> > spanning more than one core (tested on TX2 as well).
> >
> > So you'd only hit this if LLC and cluster level span the same cores (a
> > single core in this case, for non-cluster), in the presence of SMT.
> >
>
> Not sure I understand it correctly but in the below case I think the LLC may span
> the same core with socket?
Ah, I've jumped to conclusions based on the "non-cluster" mention. Does
"non-cluster" just mean that there's no intermediary "cluster" grouping of
CPUs between core and LLC? How does the PPTT table look like, by the
way?
Thanks,
Ionela.
>
> > Reviewed-by: Ionela Voinescu <ionela.voinescu@arm.com>
> >
> > Many thanks,
> > Ionela.
> >
> >> Test with:
> >> qemu-system-aarch64 -enable-kvm -machine virt \
> >> -net none \
> >> -cpu host \
> >> -bios ./QEMU_EFI.fd \
> >> -m 2G \
> >> -smp 48,sockets=2,cores=12,threads=2 \
> >> -kernel $Image \
> >> -initrd $Rootfs \
> >> -nographic
> >> -append "rdinit=init console=ttyAMA0 sched_verbose loglevel=8"
> >>
> >> We'll get below error:
> >> [ 3.084568] BUG: arch topology borken
> >> [ 3.084570] the SMT domain not a subset of the CLS domain
> >>
> >> Since cluster is a level higher than SMT, fix this by making cluster
> >> spans at least SMT CPUs.
> >>
> >> Cc: Sudeep Holla <sudeep.holla@arm.com>
> >> Cc: Vincent Guittot <vincent.guittot@linaro.org>
> >> Cc: Ionela Voinescu <ionela.voinescu@arm.com>
> >> Fixes: bfcc4397435d ("arch_topology: Limit span of cpu_clustergroup_mask()")
> >> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
> >> ---
> >> drivers/base/arch_topology.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> >> index 0424b59b695e..0056a1273275 100644
> >> --- a/drivers/base/arch_topology.c
> >> +++ b/drivers/base/arch_topology.c
> >> @@ -724,7 +724,7 @@ const struct cpumask *cpu_clustergroup_mask(int cpu)
> >> */
> >> if (cpumask_subset(cpu_coregroup_mask(cpu),
> >> &cpu_topology[cpu].cluster_sibling))
> >> - return get_cpu_mask(cpu);
> >> + return cpu_smt_mask(cpu);
> >>
> >> return &cpu_topology[cpu].cluster_sibling;
> >> }
> >> --
> >> 2.24.0
> >>
> >
> > .
> >
next prev parent reply other threads:[~2022-08-23 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:30 Yicong Yang
2022-08-23 8:06 ` Ionela Voinescu
2022-08-23 13:05 ` Yicong Yang
2022-08-23 17:53 ` Ionela Voinescu [this message]
2022-08-24 1:31 ` Yicong Yang
2022-08-23 9:22 ` Sudeep Holla
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=YwUUEzULS1ha1rqY@arm.com \
--to=ionela.voinescu@arm.com \
--cc=21cnbao@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@huawei.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.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®