From: Brian Geffon <bgeffon@google.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Martin Cracauer <cracauer@cons.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Johannes Weiner <hannes@cmpxchg.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
David Hildenbrand <david@redhat.com>,
Bobby Powers <bobbypowers@gmail.com>,
Maya Gokhale <gokhale2@llnl.gov>,
Jerome Glisse <jglisse@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Marty McFadden <mcfadden8@llnl.gov>, Mel Gorman <mgorman@suse.de>,
Hugh Dickins <hughd@google.com>,
Denis Plotnikov <dplotnikov@virtuozzo.com>,
Pavel Emelyanov <xemul@virtuozzo.com>
Subject: Re: [PATCH RESEND v6 00/16] mm: Page fault enhancements
Date: Fri, 21 Feb 2020 11:26:12 -0800 [thread overview]
Message-ID: <CADyq12wFKwzUYipU4g4Ey9X9J3qY0S=PEhSMBAeLfzpETUWVWQ@mail.gmail.com> (raw)
In-Reply-To: <20200220155353.8676-1-peterx@redhat.com>
I tested the entire patchset because I'm very interested in fault
retries with userfaultfd and the series has been stable and worked
well on x86.
Tested-by: Brian Geffon <bgeffon@google.com>
On Thu, Feb 20, 2020 at 7:54 AM Peter Xu <peterx@redhat.com> wrote:
>
> [Resend v6]
>
> This is v6 of the series. It is majorly a rebase to 5.6-rc2, nothing
> else to be expected (plus some tests after the rebase). Instead of
> rewrite the cover letter I decided to use what we have for v5.
>
> Adding extra CCs for both Bobby Powers <bobbypowers@gmail.com> and
> Brian Geffon <bgeffon@google.com>.
>
> Online repo: https://github.com/xzpeter/linux/tree/mm-pf-signal-retry
>
> Any review comment is appreciated. Thanks,
>
> =============== v5 cover letter ==================
>
> This is v5 of the series. As Matthew suggested, I split the previous
> patch "mm: Return faster for non-fatal signals in user mode faults"
> into a few smaller ones:
>
> 1. One patch to introduce fatal_signal_pending(), and use it in
> archs that can directly apply
>
> 2. A few more patches to let the rest archs to use the new helper.
> With that we can have an unified entry for signal detection
>
> 3. One last patch to change fatal_signal_pending() to detect
> userspace non-fatal signal
>
> Nothing should have changed in the rest patches. Because the fault
> retry patches will depend on the previous ones, I decided to simply
> repost all the patches.
>
> Here's the new patchset layout:
>
> Patch 1-2: cleanup, and potential bugfix of hugetlbfs on fault retry
>
> Patch 3-9: let page fault to respond to non-fatal signals faster
>
> Patch 10: remove the userfaultfd NOPAGE emulation
>
> Patch 11-14: allow page fault to retry more than once
>
> Patch 15-16: let gup code to use FAULT_FLAG_KILLABLE too
>
> I would really appreciate any review comments for the series,
> especially for the first two patches which IMHO are even not related
> to this patchset and they should either cleanup or fix things.
>
> Smoke tested on x86 only.
>
> Thanks,
>
> v5:
> - split "mm: Return faster for non-fatal signals in user mode faults"
> into a few more patches, let all archs to use an unified entry for
> fast signal handling (fatal_signal_pending)
>
> v4:
> - use lore.kernel.org for all the links in commit messages [Kirill]
> - one more patch ("mm/gup: Fix __get_user_pages() on fault retry of
> hugetlb") to fix hugetlb path on fault retry
> - one more patch ("mm/gup: Allow to react to fatal signals") to:
> - use down_read_killable() properly [Linus]
> - pass in FAULT_FLAG_KILLABLE for all GUP [Linus]
> - one more patch ("mm/userfaultfd: Honor FAULT_FLAG_KILLABLE in fault
> path") to let handle_userfaultfd() respect FAULT_FLAG_KILLABLE.
> Should have no functional change after previous two new patches.
>
> v3:
> - check fatal signals in __get_user_page_locked() [Linus]
> - add r-bs
>
> v2:
> - resent previous version, rebase only
>
> =============== v1 cover letter ==================
>
> This series is split out of userfaultfd-wp series to only cover the
> general page fault changes, since it seems to make sense itself.
>
> Basically it does two things:
>
> (a) Allows the page fault handlers to be more interactive on not
> only SIGKILL, but also the rest of userspace signals (especially
> for user-mode faults), and,
>
> (b) Allows the page fault retry (VM_FAULT_RETRY) to happen for more
> than once.
>
> I'm keeping the CC list as in uffd-wp v5, hopefully I'm not sending
> too much spams...
>
> And, instead of writting again the cover letter, I'm just copy-pasting
> my previous link here which has more details on why we do this:
>
> https://patchwork.kernel.org/cover/10691991/
>
> The major change from that latest version should be that we introduced
> a new page fault flag FAULT_FLAG_INTERRUPTIBLE as suggested by Linus
> [1] to represents that we would like the fault handler to respond to
> non-fatal signals. Also, we're more careful now on when to do the
> immediate return of the page fault for such signals. For example, now
> we'll only check against signal_pending() for user-mode page faults
> and we keep the kernel-mode page fault patch untouched for it. More
> information can be found in separate patches.
>
> The patchset is only lightly tested on x86.
>
> All comments are greatly welcomed. Thanks,
>
> [1] https://lkml.org/lkml/2019/6/25/1382
>
> Peter Xu (16):
> mm/gup: Rename "nonblocking" to "locked" where proper
> mm/gup: Fix __get_user_pages() on fault retry of hugetlb
> mm: Introduce fault_signal_pending()
> x86/mm: Use helper fault_signal_pending()
> arc/mm: Use helper fault_signal_pending()
> arm64/mm: Use helper fault_signal_pending()
> powerpc/mm: Use helper fault_signal_pending()
> sh/mm: Use helper fault_signal_pending()
> mm: Return faster for non-fatal signals in user mode faults
> userfaultfd: Don't retake mmap_sem to emulate NOPAGE
> mm: Introduce FAULT_FLAG_DEFAULT
> mm: Introduce FAULT_FLAG_INTERRUPTIBLE
> mm: Allow VM_FAULT_RETRY for multiple times
> mm/gup: Allow VM_FAULT_RETRY for multiple times
> mm/gup: Allow to react to fatal signals
> mm/userfaultfd: Honor FAULT_FLAG_KILLABLE in fault path
>
> arch/alpha/mm/fault.c | 6 +--
> arch/arc/mm/fault.c | 35 +++++--------
> arch/arm/mm/fault.c | 7 +--
> arch/arm64/mm/fault.c | 26 +++------
> arch/hexagon/mm/vm_fault.c | 5 +-
> arch/ia64/mm/fault.c | 5 +-
> arch/m68k/mm/fault.c | 7 +--
> arch/microblaze/mm/fault.c | 5 +-
> arch/mips/mm/fault.c | 5 +-
> arch/nds32/mm/fault.c | 5 +-
> arch/nios2/mm/fault.c | 7 +--
> arch/openrisc/mm/fault.c | 5 +-
> arch/parisc/mm/fault.c | 8 ++-
> arch/powerpc/mm/fault.c | 20 ++-----
> arch/riscv/mm/fault.c | 9 +---
> arch/s390/mm/fault.c | 10 ++--
> arch/sh/mm/fault.c | 13 +++--
> arch/sparc/mm/fault_32.c | 5 +-
> arch/sparc/mm/fault_64.c | 5 +-
> arch/um/kernel/trap.c | 3 +-
> arch/unicore32/mm/fault.c | 8 ++-
> arch/x86/mm/fault.c | 30 +++++------
> arch/xtensa/mm/fault.c | 5 +-
> drivers/gpu/drm/ttm/ttm_bo_vm.c | 12 +++--
> fs/userfaultfd.c | 62 ++++++++++------------
> include/linux/mm.h | 81 ++++++++++++++++++++++++----
> include/linux/sched/signal.h | 14 +++++
> mm/filemap.c | 2 +-
> mm/gup.c | 93 +++++++++++++++++++++------------
> mm/hugetlb.c | 17 +++---
> mm/internal.h | 6 +--
> 31 files changed, 281 insertions(+), 240 deletions(-)
>
> --
> 2.24.1
>
next prev parent reply other threads:[~2020-02-21 19:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:53 [PATCH RESEND v6 00/16] mm: Page fault enhancements Peter Xu
2020-02-20 15:53 ` [PATCH RESEND v6 01/16] mm/gup: Rename "nonblocking" to "locked" where proper Peter Xu
2020-02-20 15:53 ` [PATCH RESEND v6 02/16] mm/gup: Fix __get_user_pages() on fault retry of hugetlb Peter Xu
2020-03-02 19:02 ` David Hildenbrand
2020-03-02 20:07 ` Peter Xu
2020-03-02 20:22 ` David Hildenbrand
2020-02-20 15:53 ` [PATCH RESEND v6 03/16] mm: Introduce fault_signal_pending() Peter Xu
2020-03-02 19:04 ` David Hildenbrand
2020-02-20 15:53 ` [PATCH RESEND v6 04/16] x86/mm: Use helper fault_signal_pending() Peter Xu
2020-02-20 15:58 ` [PATCH RESEND v6 05/16] arc/mm: " Peter Xu
2020-02-20 15:59 ` [PATCH RESEND v6 06/16] arm64/mm: " Peter Xu
2020-02-20 16:02 ` [PATCH RESEND v6 07/16] powerpc/mm: " Peter Xu
2020-02-20 16:02 ` [PATCH RESEND v6 08/16] sh/mm: " Peter Xu
2020-02-20 16:02 ` [PATCH RESEND v6 09/16] mm: Return faster for non-fatal signals in user mode faults Peter Xu
2020-02-20 16:02 ` [PATCH RESEND v6 10/16] userfaultfd: Don't retake mmap_sem to emulate NOPAGE Peter Xu
2020-02-20 16:02 ` [PATCH RESEND v6 11/16] mm: Introduce FAULT_FLAG_DEFAULT Peter Xu
2020-02-20 16:02 ` [PATCH RESEND v6 13/16] mm: Allow VM_FAULT_RETRY for multiple times Peter Xu
2020-02-20 16:02 ` [PATCH RESEND v6 15/16] mm/gup: Allow to react to fatal signals Peter Xu
2020-02-20 16:03 ` [PATCH RESEND v6 16/16] mm/userfaultfd: Honor FAULT_FLAG_KILLABLE in fault path Peter Xu
2020-02-20 19:53 ` [PATCH RESEND v6 12/16] mm: Introduce FAULT_FLAG_INTERRUPTIBLE Peter Xu
2020-02-20 19:53 ` [PATCH RESEND v6 14/16] mm/gup: Allow VM_FAULT_RETRY for multiple times Peter Xu
2020-02-21 19:26 ` Brian Geffon [this message]
2020-03-02 17:31 ` [PATCH RESEND v6 00/16] mm: Page fault enhancements Peter Xu
2020-02-21 19:32 ` Linus Torvalds
2020-02-21 20:11 ` Peter Xu
2020-03-07 20:33 ` David Hildenbrand
2020-03-07 21:47 ` Peter Xu
2020-03-08 12:12 ` David Hildenbrand
2020-03-09 19:51 ` Peter Xu
2020-03-09 20:06 ` David Hildenbrand
2020-03-08 12:49 ` David Hildenbrand
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='CADyq12wFKwzUYipU4g4Ey9X9J3qY0S=PEhSMBAeLfzpETUWVWQ@mail.gmail.com' \
--to=bgeffon@google.com \
--cc=aarcange@redhat.com \
--cc=bobbypowers@gmail.com \
--cc=cracauer@cons.org \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=dplotnikov@virtuozzo.com \
--cc=gokhale2@llnl.gov \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcfadden8@llnl.gov \
--cc=mgorman@suse.de \
--cc=mike.kravetz@oracle.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
--cc=xemul@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).