From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: <will@kernel.org>, <catalin.marinas@arm.com>,
<ryabinin.a.a@gmail.com>, <andreyknvl@gmail.com>,
<dvyukov@google.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<elver@google.com>, <akpm@linux-foundation.org>,
<gregkh@linuxfoundation.org>
Cc: <kasan-dev@googlegroups.com>
Subject: Re: [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator
Date: Wed, 15 Sep 2021 16:33:09 +0800 [thread overview]
Message-ID: <c06faf6c-3d21-04f2-6855-95c86e96cf5a@huawei.com> (raw)
In-Reply-To: <20210910053354.26721-1-wangkefeng.wang@huawei.com>
Hi Greg and Andrew, as Catalin saids,the series touches drivers/ and mm/
but missing
acks from both of you,could you take a look of this patchset(patch1
change mm/vmalloc.c
and patch2 changes drivers/base/arch_numa.c).
And Catalin, is there any other comments? I hope this could be merged
into next version,
Many thanks all of you.
On 2021/9/10 13:33, Kefeng Wang wrote:
> Percpu embedded first chunk allocator is the firstly option, but it
> could fails on ARM64, eg,
> "percpu: max_distance=0x5fcfdc640000 too large for vmalloc space 0x781fefff0000"
> "percpu: max_distance=0x600000540000 too large for vmalloc space 0x7dffb7ff0000"
> "percpu: max_distance=0x5fff9adb0000 too large for vmalloc space 0x5dffb7ff0000"
>
> then we could meet "WARNING: CPU: 15 PID: 461 at vmalloc.c:3087 pcpu_get_vm_areas+0x488/0x838",
> even the system could not boot successfully.
>
> Let's implement page mapping percpu first chunk allocator as a fallback
> to the embedding allocator to increase the robustness of the system.
>
> Also fix a crash when both NEED_PER_CPU_PAGE_FIRST_CHUNK and KASAN_VMALLOC enabled.
>
> Tested on ARM64 qemu with cmdline "percpu_alloc=page" based on v5.14.
>
> V4:
> - add ACK/RB
> - address comments about patch1 from Catalin
> - add Greg and Andrew into list suggested by Catalin
>
> v3:
> - search for a range that fits instead of always picking the end from
> vmalloc area suggested by Catalin.
> - use NUMA_NO_NODE to avoid "virt_to_phys used for non-linear address:"
> issue in arm64 kasan_populate_early_vm_area_shadow().
> - add Acked-by: Marco Elver <elver@google.com> to patch v3
>
> V2:
> - fix build error when CONFIG_KASAN disabled, found by lkp@intel.com
> - drop wrong __weak comment from kasan_populate_early_vm_area_shadow(),
> found by Marco Elver <elver@google.com>
>
> Kefeng Wang (3):
> vmalloc: Choose a better start address in vm_area_register_early()
> arm64: Support page mapping percpu first chunk allocator
> kasan: arm64: Fix pcpu_page_first_chunk crash with KASAN_VMALLOC
>
> arch/arm64/Kconfig | 4 ++
> arch/arm64/mm/kasan_init.c | 16 ++++++++
> drivers/base/arch_numa.c | 82 +++++++++++++++++++++++++++++++++-----
> include/linux/kasan.h | 6 +++
> mm/kasan/init.c | 5 +++
> mm/vmalloc.c | 19 ++++++---
> 6 files changed, 116 insertions(+), 16 deletions(-)
>
_______________________________________________
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-09-15 8:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 5:33 [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator Kefeng Wang
2021-09-10 5:33 ` [PATCH v4 1/3] vmalloc: Choose a better start address in vm_area_register_early() Kefeng Wang
2021-10-12 18:21 ` Catalin Marinas
2021-09-10 5:33 ` [PATCH v4 2/3] arm64: Support page mapping percpu first chunk allocator Kefeng Wang
2021-09-17 6:24 ` Greg KH
2021-09-17 6:55 ` Kefeng Wang
2021-09-17 7:04 ` Greg KH
2021-09-17 7:24 ` Kefeng Wang
2021-09-10 5:33 ` [PATCH v4 3/3] kasan: arm64: Fix pcpu_page_first_chunk crash with KASAN_VMALLOC Kefeng Wang
2021-10-12 18:17 ` Catalin Marinas
2021-10-13 1:09 ` Kefeng Wang
2021-09-15 8:33 ` Kefeng Wang [this message]
2021-09-16 15:41 ` [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator Greg KH
[not found] ` <525cb266-ecfc-284e-d701-4a8b40fe413b@huawei.com>
2021-09-17 6:24 ` Greg KH
2021-09-28 7:48 ` Kefeng Wang
2021-10-08 13:33 ` Kefeng Wang
2021-10-10 21:36 ` Andrew Morton
2021-10-11 1:09 ` Kefeng Wang
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=c06faf6c-3d21-04f2-6855-95c86e96cf5a@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.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;
as well as URLs for NNTP newsgroup(s).