From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Pavel Emelyanov <xemul@virtuozzo.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH 0/3] userfaultfd: selftest: add event tests
Date: Sun, 28 Aug 2016 17:37:44 +0300 [thread overview]
Message-ID: <1472395067-24538-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)
Hi,
These patches add tests for userfaultfd events used in non-cooperative
scenario.
The tests verify that fork(), mremap() and madvise(MADV_DONTNEED) can be
properly handled when the process that monitors userfaultfd is not the
process that causes the pagefaults.
Mike Rapoport (3):
userfaultfd: selftest: introduce userfaultfd_open
userfaultfd: selftest: add ufd parameter to copy_page
userfaultfd: selftest: add test for FORK, MADVDONTNEED and REMAP events
tools/testing/selftests/vm/userfaultfd.c | 219 ++++++++++++++++++++++++++-----
1 file changed, 189 insertions(+), 30 deletions(-)
--
1.9.1
--
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:[~2016-08-28 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 14:37 Mike Rapoport [this message]
2016-08-28 14:37 ` [PATCH 1/3] userfaultfd: selftest: introduce userfaultfd_open Mike Rapoport
2016-08-28 14:37 ` [PATCH 2/3] userfaultfd: selftest: add ufd parameter to copy_page Mike Rapoport
2016-08-28 14:37 ` [PATCH 3/3] userfaultfd: selftest: add test for FORK, MADVDONTNEED and REMAP events 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=1472395067-24538-1-git-send-email-rppt@linux.vnet.ibm.com \
--to=rppt@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--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: 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