From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f197.google.com (mail-pf0-f197.google.com [209.85.192.197]) by kanga.kvack.org (Postfix) with ESMTP id 4B99A6B03A3 for ; Tue, 16 May 2017 06:36:12 -0400 (EDT) Received: by mail-pf0-f197.google.com with SMTP id p74so122066886pfd.11 for ; Tue, 16 May 2017 03:36:12 -0700 (PDT) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com. [148.163.156.1]) by mx.google.com with ESMTPS id 3si13084591plo.11.2017.05.16.03.36.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 May 2017 03:36:11 -0700 (PDT) Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v4GAT55N066278 for ; Tue, 16 May 2017 06:36:11 -0400 Received: from e06smtp15.uk.ibm.com (e06smtp15.uk.ibm.com [195.75.94.111]) by mx0a-001b2d01.pphosted.com with ESMTP id 2afmqsvg1f-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 16 May 2017 06:36:10 -0400 Received: from localhost by e06smtp15.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 16 May 2017 11:36:08 +0100 From: "Mike Rapoport" Subject: [RFC PATCH 0/5] userfaultfd: non-cooperative: syncronous events Date: Tue, 16 May 2017 13:35:57 +0300 Message-Id: <1494930962-3318-1-git-send-email-rppt@linux.vnet.ibm.com> Sender: owner-linux-mm@kvack.org List-ID: To: Andrea Arcangeli Cc: Pavel Emelyanov , linux-mm , Mike Rapoport Hi, These patches add ability to generate userfaultfd events so that thier processing will be synchronized with the non-cooperative thread that caused the event. In the non-cooperative case userfaultfd resumes execution of the thread that caused an event when the notification is read() by the uffd monitor. In some cases, like, for example, madvise(MADV_REMOVE), it might be desirable to keep the thread that caused the event suspended until the uffd monitor had the event handled. The first two patches just shuffle the code a bit to make subsequent changes easier. The patches 3 and 4 create some unification in the way the threads are queued into waitqueues either after page fault or after a non-cooperative event. The fifth patch extends the userfaultfd API with an implementation of UFFD_EVENT_REMOVE_SYNC that allows to keep the thread that triggered UFFD_EVENT_REMOVE until the uffd monitor would not wake it explicitly. Mike Rapoport (5): userfaultfd: introduce userfault_init_waitqueue helper userfaultfd: introduce userfaultfd_should_wait helper userfaultfd: non-cooperative: generalize wake key structure userfaultfd: non-cooperative: use fault_pending_wqh for all events userfaultfd: non-cooperative: allow synchronous EVENT_REMOVE fs/userfaultfd.c | 205 ++++++++++++++++++++++++--------------- include/uapi/linux/userfaultfd.h | 11 +++ 2 files changed, 136 insertions(+), 80 deletions(-) -- 2.7.4 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org