From: Pierre Gondois <pierre.gondois@arm.com>
To: Radu Rendec <rrendec@redhat.com>, linux-kernel@vger.kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] arch_topology: Pre-allocate cacheinfo from primary CPU
Date: Tue, 11 Apr 2023 14:36:14 +0200 [thread overview]
Message-ID: <dea94484-797f-3034-7b86-6d88801c0d91@arm.com> (raw)
In-Reply-To: <20230406233926.1670094-1-rrendec@redhat.com>
Hello Radu,
Some additional points:
1-
For the record, Will made a comment about adding weak functions
(cf. https://lore.kernel.org/all/20230327121734.GB31342@willie-the-truck/)
but I don't see how it could be done otherwise ...
2-
The patch-set needs to be rebased on top of v6.3-rc6,
otherwise there is a merge conflict.
3-
When trying the patch-set on an ACPI platform with no PPTT, it seems that
fetch_cache_info() is not called from init_cpu_topology() because
parse_acpi_topology() returns an error code. This result in a
'sleeping function called from invalid context' message. The following made
it work for me:
--- a/drivers/base/arch_topology.c
+++ b/drivers/base/arch_topology.c
@@ -838,7 +838,6 @@ void __init init_cpu_topology(void)
* don't use partial information.
*/
reset_cpu_topology();
- return;
}
for_each_possible_cpu(cpu) {
With 2 and 3 addressed:
Reviewed-by: Pierre Gondois <pierre.gondois@arm.com>
Also maybe wait for Sudeep to have a look before sending a v4,
Regards,
Pierre
On 4/7/23 01:39, Radu Rendec wrote:
> Commit 5944ce092b97 ("arch_topology: Build cacheinfo from primary CPU")
> tries to build the cacheinfo from the primary CPU prior to secondary
> CPUs boot, if the DT/ACPI description contains cache information.
> However, if such information is not present, it still reverts to the old
> behavior, which allocates the cacheinfo memory on each secondary CPU. On
> RT kernels, this triggers a "BUG: sleeping function called from invalid
> context" because the allocation is done before preemption is first
> enabled on the secondary CPU.
>
> The solution is to add cache information to DT/ACPI, but at least on
> arm64 systems this can be avoided by leveraging automatic detection
> (through the CLIDR_EL1 register), which is already implemented but
> currently doesn't work on RT kernels for the reason described above.
>
> This patch series attempts to enable automatic detection for RT kernels
> when no DT/ACPI cache information is available, by pre-allocating
> cacheinfo memory on the primary CPU.
>
> The first patch adds an architecture independent infrastructure that
> allows architecture specific code to take an early guess at the number
> of cache leaves of the secodary CPUs, while it runs in preemptible
> context on the primary CPU. At the same time, it gives architecture
> specific code the opportunity to go back later, while it runs on the
> secondary CPU, and reallocate the cacheinfo memory if the initial guess
> proves to be wrong.
>
> The second patch leverages the infrastructure implemented in the first
> patch and enables early cache depth detection for arm64.
>
> The patch series is based on an RFC patch that was posted to the
> linux-arm-kernel mailing list and discussed with a smaller audience:
> https://lore.kernel.org/all/20230323224242.31142-1-rrendec@redhat.com/
>
> Changes to v2:
> * Address minor coding style issue (unbalanced braces).
> * Move cacheinfo reallocation logic from detect_cache_attributes() to a
> new function to improve code readability.
> * Minor fix to cacheinfo reallocation logic to avoid a new detection of
> the cache level if/when detect_cache_attributes() is called again.
>
> Radu Rendec (2):
> cacheinfo: Add arch specific early level initializer
> cacheinfo: Add arm64 early level initializer implementation
>
> arch/arm64/kernel/cacheinfo.c | 32 +++++++++++----
> drivers/base/cacheinfo.c | 75 +++++++++++++++++++++++++----------
> include/linux/cacheinfo.h | 2 +
> 3 files changed, 79 insertions(+), 30 deletions(-)
>
next prev parent reply other threads:[~2023-04-11 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 23:39 Radu Rendec
2023-04-06 23:39 ` [PATCH v3 1/2] cacheinfo: Add arch specific early level initializer Radu Rendec
2023-04-12 11:36 ` Sudeep Holla
2023-04-12 13:30 ` Radu Rendec
2023-04-06 23:39 ` [PATCH v3 2/2] cacheinfo: Add arm64 early level initializer implementation Radu Rendec
2023-04-12 11:40 ` Sudeep Holla
2023-04-12 13:36 ` Radu Rendec
2023-04-11 12:36 ` Pierre Gondois [this message]
2023-04-11 16:36 ` [PATCH v3 0/2] arch_topology: Pre-allocate cacheinfo from primary CPU 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=dea94484-797f-3034-7b86-6d88801c0d91@arm.com \
--to=pierre.gondois@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrendec@redhat.com \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
/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®