From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Qing Wang <wangqing@vivo.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] arch_topology: Use llc_id instead of package_id
Date: Fri, 13 May 2022 12:42:00 +0200 [thread overview]
Message-ID: <afafbb0c-5279-bee8-1ef4-434733e2a552@arm.com> (raw)
In-Reply-To: <20220513090330.z25fwthekn4rjkwq@bogus>
On 13/05/2022 11:03, Sudeep Holla wrote:
> On Fri, May 13, 2022 at 10:34:00AM +0200, Dietmar Eggemann wrote:
[...]
>> @@ -527,7 +528,8 @@ static int __init parse_core(struct device_node *core, int package_id,
>> return -EINVAL;
>> }
>>
>> - cpu_topology[cpu].package_id = package_id;
>> + cpu_topology[cpu].package_id = 0;
>
> While the above looks good and matches with what I am attempting to do
> as well ...
>
>> + cpu_topology[cpu].llc_id = llc_id;
>
> This looks wrong for simple reason that this is derived incorrectly from
> the cpu-map while there is no guarantee that it matches the last level
> cache ID on the system as we didn't parse the cache topology for this.
> So I disagree with this change as it might conflict with the actual and
> correct llc_id.
It might not match the LLC, that's true. Something we have already today
in Android for DynamIQ clusters with big/Little. People using 1. level
clusters to group CPUs according to uArch.
My point is we manage to get:
SMT - cpu_smt_mask()
CLS - cpu_clustergroup_mask()
MC - cpu_coregroup_mask()
DIE - cpu_cpu_mask()
covered in ACPI with the cpu_topology[] structure and if we want CLS on
DT we have to save cluster_id for the 2. level (DT) cluster.
And that's why I proposed to (ab)use llc_id to form the MC mask.
I'm not currently aware of another solution to get CLS somehow elegantly
into a DT system.
next prev parent reply other threads:[~2022-05-13 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 8:34 Dietmar Eggemann
2022-05-13 9:03 ` Sudeep Holla
2022-05-13 10:42 ` Dietmar Eggemann [this message]
2022-05-13 11:03 ` Sudeep Holla
2022-05-13 12:04 ` Dietmar Eggemann
2022-05-16 10:35 ` Sudeep Holla
2022-05-17 9:14 ` Dietmar Eggemann
2022-05-17 10:57 ` Sudeep Holla
2022-05-18 10:23 ` Dietmar Eggemann
2022-05-18 10:43 ` Sudeep Holla
2022-05-18 15:54 ` Dietmar Eggemann
2022-05-19 9:21 ` 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=afafbb0c-5279-bee8-1ef4-434733e2a552@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=wangqing@vivo.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®