From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>,
<surenb@google.com>
Cc: Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
<x86@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <loongarch@lists.linux.dev>,
<linuxppc-dev@lists.ozlabs.org>,
<linux-riscv@lists.infradead.org>, <linux-s390@vger.kernel.org>
Subject: Re: [PATCH rfc -next 00/10] mm: convert to generic VMA lock-based page fault
Date: Thu, 13 Jul 2023 19:46:40 +0800 [thread overview]
Message-ID: <699d421a-b8cf-a338-5736-acc25f671c57@huawei.com> (raw)
In-Reply-To: <20230713095155.189443-1-wangkefeng.wang@huawei.com>
Please ignore this one...
On 2023/7/13 17:51, Kefeng Wang wrote:
> Add a generic VMA lock-based page fault handler in mm core, and convert
> architectures to use it, which eliminate architectures's duplicated codes.
>
> With it, we can avoid multiple changes in architectures's code if we
> add new feature or bugfix.
>
> This fixes riscv missing change about commit 38b3aec8e8d2 "mm: drop per-VMA
> lock when returning VM_FAULT_RETRY or VM_FAULT_COMPLETED", and in the end,
> we enable this feature on ARM32/Loongarch too.
>
> This is based on next-20230713, only built test(no loongarch compiler,
> so except loongarch).
>
> Kefeng Wang (10):
> mm: add a generic VMA lock-based page fault handler
> x86: mm: use try_vma_locked_page_fault()
> arm64: mm: use try_vma_locked_page_fault()
> s390: mm: use try_vma_locked_page_fault()
> powerpc: mm: use try_vma_locked_page_fault()
> riscv: mm: use try_vma_locked_page_fault()
> ARM: mm: try VMA lock-based page fault handling first
> loongarch: mm: cleanup __do_page_fault()
> loongarch: mm: add access_error() helper
> loongarch: mm: try VMA lock-based page fault handling first
>
> arch/arm/Kconfig | 1 +
> arch/arm/mm/fault.c | 15 ++++++-
> arch/arm64/mm/fault.c | 28 +++---------
> arch/loongarch/Kconfig | 1 +
> arch/loongarch/mm/fault.c | 92 ++++++++++++++++++++++++---------------
> arch/powerpc/mm/fault.c | 54 ++++++++++-------------
> arch/riscv/mm/fault.c | 38 +++++++---------
> arch/s390/mm/fault.c | 23 +++-------
> arch/x86/mm/fault.c | 39 +++++++----------
> include/linux/mm.h | 28 ++++++++++++
> mm/memory.c | 42 ++++++++++++++++++
> 11 files changed, 206 insertions(+), 155 deletions(-)
>
next prev parent reply other threads:[~2023-07-13 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 9:51 Kefeng Wang
2023-07-13 11:46 ` Kefeng Wang [this message]
2023-07-13 9:53 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=699d421a-b8cf-a338-5736-acc25f671c57@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kernel@xen0n.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=surenb@google.com \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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