From: Mike Rapoport <rppt@linux.vnet.ibm.com> To: Andrew Morton <akpm@linux-foundation.org>, Andrea Arcangeli <aarcange@redhat.com> Cc: Pavel Emelyanov <xemul@virtuozzo.com>, linux-mm <linux-mm@kvack.org>, linux-api <linux-api@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>, crml <criu@openvz.org>, Mike Rapoport <rppt@linux.vnet.ibm.com> Subject: [PATCH 0/3] userfaultfd: non-cooperative: syncronous events Date: Tue, 27 Feb 2018 10:19:49 +0200 [thread overview] Message-ID: <1519719592-22668-1-git-send-email-rppt@linux.vnet.ibm.com> (raw) Hi, These patches add ability to generate userfaultfd events so that their 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 to avoid races between the thread that caused the and userfaultfd ioctls. Theses patches extend 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 (3): userfaultfd: introduce userfaultfd_init_waitqueue helper userfaultfd: non-cooperative: generalize wake key structure userfaultfd: non-cooperative: allow synchronous EVENT_REMOVE fs/userfaultfd.c | 191 +++++++++++++++++++++++++++++---------- include/uapi/linux/userfaultfd.h | 14 +++ 2 files changed, 158 insertions(+), 47 deletions(-) -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@linux.vnet.ibm.com> To: Andrew Morton <akpm@linux-foundation.org>, Andrea Arcangeli <aarcange@redhat.com> Cc: Pavel Emelyanov <xemul@virtuozzo.com>, linux-mm <linux-mm@kvack.org>, linux-api <linux-api@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>, crml <criu@openvz.org>, Mike Rapoport <rppt@linux.vnet.ibm.com> Subject: [PATCH 0/3] userfaultfd: non-cooperative: syncronous events Date: Tue, 27 Feb 2018 10:19:49 +0200 [thread overview] Message-ID: <1519719592-22668-1-git-send-email-rppt@linux.vnet.ibm.com> (raw) Hi, These patches add ability to generate userfaultfd events so that their 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 to avoid races between the thread that caused the and userfaultfd ioctls. Theses patches extend 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 (3): userfaultfd: introduce userfaultfd_init_waitqueue helper userfaultfd: non-cooperative: generalize wake key structure userfaultfd: non-cooperative: allow synchronous EVENT_REMOVE fs/userfaultfd.c | 191 +++++++++++++++++++++++++++++---------- include/uapi/linux/userfaultfd.h | 14 +++ 2 files changed, 158 insertions(+), 47 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2018-02-27 8:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-27 8:19 Mike Rapoport [this message] 2018-02-27 8:19 ` [PATCH 0/3] userfaultfd: non-cooperative: syncronous events Mike Rapoport 2018-02-27 8:19 ` [PATCH 1/3] userfaultfd: introduce userfaultfd_init_waitqueue helper Mike Rapoport 2018-02-27 8:19 ` Mike Rapoport 2018-02-27 8:19 ` [PATCH 2/3] userfaultfd: non-cooperative: generalize wake key structure Mike Rapoport 2018-02-27 8:19 ` Mike Rapoport 2018-02-27 8:19 ` [PATCH 3/3] userfaultfd: non-cooperative: allow synchronous EVENT_REMOVE Mike Rapoport 2018-02-27 8:19 ` Mike Rapoport 2018-02-28 8:21 ` Pavel Emelyanov 2018-02-28 8:21 ` Pavel Emelyanov 2018-02-28 8:26 ` Mike Rapoport 2018-02-28 8:26 ` Mike Rapoport 2018-03-02 23:38 ` [PATCH 0/3] userfaultfd: non-cooperative: syncronous events Andrew Morton 2018-03-02 23:38 ` Andrew Morton 2018-03-03 9:09 ` Mike Rapoport 2018-03-03 9:09 ` Mike Rapoport
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=1519719592-22668-1-git-send-email-rppt@linux.vnet.ibm.com \ --to=rppt@linux.vnet.ibm.com \ --cc=aarcange@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=criu@openvz.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.