From: Alexey Perevalov <a.perevalov@samsung.com>
To: Andrea Arcangeli <aarcange@redhat.com>, linux-mm@kvack.org
Cc: Alexey Perevalov <a.perevalov@samsung.com>,
rppt@linux.vnet.ibm.com, mike.kravetz@oracle.com,
dgilbert@redhat.com
Subject: [PATCH v3] Illuminate thread id to user space
Date: Mon, 03 Apr 2017 12:32:35 +0300 [thread overview]
Message-ID: <1491211956-6095-1-git-send-email-a.perevalov@samsung.com> (raw)
In-Reply-To: CGME20170403093307eucas1p2e1110dd2550426c53a7b8825efa34f99@eucas1p2.samsung.com
Hi Andrea,
This is third version of the patch. Modifications since previous versions:
(v3 -> v2)
- type of ptid now is __u32. As you suggested.
(v2 -> v1)
- process thread id is provided only when it was requested with
UFFD_FEATURE_THREAD_ID bit.
- pid from namespace is provided, so locking thread's gettid in namespace
and msg.arg.pagefault.ptid will be equal.
This patch is based on
git://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git userfault branch.
HEAD commit is "userfaultfd: switch to exclusive wakeup for blocking reads"
Alexey Perevalov (1):
userfaultfd: provide pid in userfault msg
fs/userfaultfd.c | 8 ++++++--
include/uapi/linux/userfaultfd.h | 8 +++++++-
2 files changed, 13 insertions(+), 3 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 parent reply other threads:[~2017-04-03 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170403093307eucas1p2e1110dd2550426c53a7b8825efa34f99@eucas1p2.samsung.com>
2017-04-03 9:32 ` Alexey Perevalov [this message]
[not found] ` <CGME20170403093318eucas1p2ebd57e5e4c33707063687ccd571f67bb@eucas1p2.samsung.com>
2017-04-03 9:32 ` [PATCH v3] userfaultfd: provide pid in userfault msg Alexey Perevalov
2017-04-04 19:04 ` Andrea Arcangeli
2017-04-05 12:42 ` Alexey Perevalov
2017-04-03 9:38 ` [PATCH v3] please don't see patch set Alexey Perevalov
2017-04-03 9:42 ` Alexey Perevalov
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=1491211956-6095-1-git-send-email-a.perevalov@samsung.com \
--to=a.perevalov@samsung.com \
--cc=aarcange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rppt@linux.vnet.ibm.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.