From: Valentin Schneider <valentin.schneider@arm.com>
To: Ruifeng Zhang <ruifeng.zhang0110@gmail.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: linux@armlinux.org.uk, sudeep.holla@arm.com,
Greg KH <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
a.p.zijlstra@chello.nl, mingo@kernel.org,
ruifeng.zhang1@unisoc.com, nianfu.bai@unisoc.com,
linux-arm-kernel@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/1] arm: topology: parse the topology from the dt
Date: Fri, 16 Apr 2021 10:32:35 +0100 [thread overview]
Message-ID: <87wnt2lglo.mognet@arm.com> (raw)
In-Reply-To: <CAG7+-3Nv=m0pd8t0eQEUv5zSeg86hfkKcs_VLzsbzWFabYbTTQ@mail.gmail.com>
On 16/04/21 15:47, Ruifeng Zhang wrote:
> For more requirements, if all cores in one physical cluster, the
> {aff2} of all cores are the same value.
> i.e. the sc9863a,
> core0: 0000000081000000
> core1: 0000000081000100
> core2: 0000000081000200
> core3: 0000000081000300
> core4: 0000000081000400
> core5: 0000000081000500
> core6: 0000000081000600
> core7: 0000000081000700
>
> According to MPIDR all cores will parse to the one cluster, but it's
> the big.LITTLE system, it's need two logic cluster for schedule or
> cpufreq.
> So I think it's better to add the logic of parse topology from DT.
Ah, so it's a slightly different issue, but still one that requires a
different means of specifying topology.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-16 9:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 12:23 [PATCH v2 0/1] arm: topology: parse the topology from the dt Ruifeng Zhang
2021-04-14 12:23 ` [PATCH v2 1/1] " Ruifeng Zhang
2021-04-14 12:38 ` Ruifeng Zhang
2021-04-15 18:09 ` Valentin Schneider
2021-04-15 18:09 ` [PATCH v2 0/1] " Valentin Schneider
2021-04-15 20:10 ` Dietmar Eggemann
2021-04-16 7:47 ` Ruifeng Zhang
2021-04-16 9:32 ` Valentin Schneider [this message]
2021-04-16 10:39 ` Dietmar Eggemann
2021-04-16 10:47 ` Valentin Schneider
2021-04-16 11:04 ` Ruifeng Zhang
2021-04-16 17:00 ` Dietmar Eggemann
2021-04-19 2:55 ` Ruifeng Zhang
2021-04-19 21:27 ` Dietmar Eggemann
2021-04-23 6:25 ` Ruifeng Zhang
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=87wnt2lglo.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@kernel.org \
--cc=nianfu.bai@unisoc.com \
--cc=rafael@kernel.org \
--cc=ruifeng.zhang0110@gmail.com \
--cc=ruifeng.zhang1@unisoc.com \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).