From: Pierre Gondois <pierre.gondois@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Radu Rendec <rrendec@redhat.com>,
linux-arm-kernel@lists.infradead.org,
Adrien Thierry <athierry@redhat.com>,
Eric Chanudet <echanude@redhat.com>
Subject: Re: [RFC PATCH] arch_topology: Pre-allocate cacheinfo from primary CPU
Date: Wed, 29 Mar 2023 17:39:58 +0200 [thread overview]
Message-ID: <eaaf5620-77d3-0e8a-aab5-e6013f71e194@arm.com> (raw)
In-Reply-To: <20230329150308.aaajdsh74olpjach@bogus>
On 3/29/23 17:03, Sudeep Holla wrote:
> On Wed, Mar 29, 2023 at 04:42:07PM +0200, Pierre Gondois wrote:
>>
>> This would mean that for all architectures, the cacheinfo would come from
>> ACPI/DT first.....
>
> x86 doesn't fall into the above category. So we need to ensure it continues
> to work with no errors.
Ok, then maybe having a second arch specific function like
init_cache_level() would work.
This function would be called in fetch_cache_info() after
init_of_cache_level()/acpi_get_cache_info() fail. It would fetch
cache info anywhere but in DT/ACPI.
Archs that don't want it would not implement it, and it would
allow the others to get the num_leaves/levels during early boot.
>
> --
> Regards,
> Sudeep
_______________________________________________
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:[~2023-03-29 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 22:42 [RFC PATCH] arch_topology: Pre-allocate cacheinfo from primary CPU Radu Rendec
2023-03-27 12:02 ` Pierre Gondois
2023-03-27 14:23 ` Radu Rendec
2023-03-29 14:42 ` Pierre Gondois
2023-03-29 15:03 ` Sudeep Holla
2023-03-29 15:39 ` Pierre Gondois [this message]
2023-03-29 21:35 ` Radu Rendec
2023-03-30 6:57 ` Pierre Gondois
2023-03-30 23:32 ` Radu Rendec
2023-03-31 14:49 ` Pierre Gondois
2023-04-03 21:25 ` Radu Rendec
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=eaaf5620-77d3-0e8a-aab5-e6013f71e194@arm.com \
--to=pierre.gondois@arm.com \
--cc=athierry@redhat.com \
--cc=echanude@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rrendec@redhat.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