riscv: Enable percpu page first chunk allocator #235
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Upstream branch: 457926b |
|
Upstream branch: 3ca112b |
bjoto
force-pushed
the
series/800200=>for-next
branch
from
dd45946
to
0b29297
Compare
|
Upstream branch: b85ea95 |
bjoto
force-pushed
the
series/800200=>for-next
branch
from
0b29297
to
0d65580
Compare
|
Upstream branch: b85ea95 |
bjoto
force-pushed
the
series/800200=>for-next
branch
from
0d65580
to
7a255e0
Compare
|
Upstream branch: 6c31291 |
bjoto
force-pushed
the
series/800200=>for-next
branch
from
7a255e0
to
0e53e8e
Compare
|
Upstream branch: f352a28 |
bjoto
force-pushed
the
series/800200=>for-next
branch
from
0e53e8e
to
be1b3ff
Compare
|
Upstream branch: f352a28 |
bjoto
force-pushed
the
series/800200=>for-next
branch
from
be1b3ff
to
71ea85d
Compare
|
Upstream branch: 5a2cf77 |
added 2 commits
January 5, 2024 22:06
The pcpu setup when using the page allocator sets up a new vmalloc mapping very early in the boot process, so early that it cannot use the flush_cache_vmap() function which may depend on structures not yet initialized (for example in riscv, we currently send an IPI to flush other cpus TLB). But on some architectures, we must call flush_cache_vmap(): for example, in riscv, some uarchs can cache invalid TLB entries so we need to flush the new established mapping to avoid taking an exception. So fix this by introducing a new function flush_cache_vmap_early() which is called right after setting the new page table entry and before accessing this new mapping. This new function implements a local flush tlb on riscv and is no-op for other architectures (same as today). Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Björn Töpel <bjorn@rivosinc.com>
As explained in commit 6ea529a ("percpu: make embedding first chunk allocator check vmalloc space size"), the embedding first chunk allocator needs the vmalloc space to be larger than the maximum distance between units which are grouped into NUMA nodes. On a very sparse NUMA configurations and a small vmalloc area (for example, it is 64GB in sv39), the allocation of dynamic percpu data in the vmalloc area could fail. So provide the pcpu page allocator as a fallback in case we fall into such a sparse configuration (which happened in arm64 as shown by commit 09cea61 ("arm64: support page mapping percpu first chunk allocator")). Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com> Signed-off-by: Björn Töpel <bjorn@rivosinc.com>
bjoto
force-pushed
the
series/800200=>for-next
branch
from
71ea85d
to
621c581
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request for series with
subject: riscv: Enable percpu page first chunk allocator
version: 1
url: https://patchwork.kernel.org/project/linux-riscv/list/?series=800200