From: Pavel Emelyanov <xemul@parallels.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Sanidhya Kashyap <sanidhya.gatech@gmail.com>
Subject: [PATCH 0/5] UserfaultFD: Extension for non cooperative uffd usage (v2)
Date: Wed, 13 May 2015 17:52:11 +0300 [thread overview]
Message-ID: <5553651B.1020909@parallels.com> (raw)
Hi,
This set is to address the issues that appear in userfaultfd usage
scenarios when the task monitoring the uffd and the mm-owner do not
cooperate to each other on VM changes such as remaps, madvises and
fork()-s.
This is the re-based set on the recent userfaultfd branch, two major
changes are:
* No need in separate API version, the uffd_msg introduced in the
current code and UFFD_API ioctl are enough for the needed extentions
* Two events added -- for mremap() and madvise() MADV_DONTNEED
More details about the particular events are in patches 3 trough 4.
Comments and suggestion are warmly welcome :)
The v1 discussion thread is here: https://lkml.org/lkml/2015/3/18/729
Thanks,
Pavel
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Emelyanov <xemul@parallels.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Sanidhya Kashyap <sanidhya.gatech@gmail.com>
Subject: [PATCH 0/5] UserfaultFD: Extension for non cooperative uffd usage (v2)
Date: Wed, 13 May 2015 17:52:11 +0300 [thread overview]
Message-ID: <5553651B.1020909@parallels.com> (raw)
Hi,
This set is to address the issues that appear in userfaultfd usage
scenarios when the task monitoring the uffd and the mm-owner do not
cooperate to each other on VM changes such as remaps, madvises and
fork()-s.
This is the re-based set on the recent userfaultfd branch, two major
changes are:
* No need in separate API version, the uffd_msg introduced in the
current code and UFFD_API ioctl are enough for the needed extentions
* Two events added -- for mremap() and madvise() MADV_DONTNEED
More details about the particular events are in patches 3 trough 4.
Comments and suggestion are warmly welcome :)
The v1 discussion thread is here: https://lkml.org/lkml/2015/3/18/729
Thanks,
Pavel
next reply other threads:[~2015-05-13 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:52 Pavel Emelyanov [this message]
2015-05-13 14:52 ` [PATCH 0/5] UserfaultFD: Extension for non cooperative uffd usage (v2) Pavel Emelyanov
2015-05-13 14:52 ` [PATCH 1/5] uffd: Split the find_userfault() routine Pavel Emelyanov
2015-05-13 14:52 ` Pavel Emelyanov
2015-05-13 14:52 ` [PATCH 2/5] uffd: Add ability to report non-PF events from uffd descriptor Pavel Emelyanov
2015-05-13 14:52 ` Pavel Emelyanov
2015-05-13 14:53 ` [PATCH 4/5] uffd: Add mremap() event Pavel Emelyanov
2015-05-13 14:53 ` Pavel Emelyanov
2015-05-13 14:53 ` [PATCH 5/5] uffd: Add madvise() event for MADV_DONTNEED request Pavel Emelyanov
2015-05-13 14:53 ` Pavel Emelyanov
2015-05-13 14:54 ` [PATCH 3/5] uffd: Add fork() event Pavel Emelyanov
2015-05-13 14:54 ` Pavel Emelyanov
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=5553651B.1020909@parallels.com \
--to=xemul@parallels.com \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sanidhya.gatech@gmail.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 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.