[lkml]   [2018]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH 0/3] userfaultfd: non-cooperative: syncronous events

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(-)


 \ /
  Last update: 2018-02-27 09:20    [W:0.062 / U:3.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site