From: Alexey Perevalov <a.perevalov@samsung.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: "Dr . David Alan Gilbert" <dgilbert@redhat.com>,
linux-mm@kvack.org, i.maximets@samsung.com,
a.perevalov@samsung.com
Subject: [PATCH v2] Illuminate thread id to user space
Date: Wed, 22 Mar 2017 21:29:05 +0300 [thread overview]
Message-ID: <1490207346-9703-1-git-send-email-a.perevalov@samsung.com> (raw)
In-Reply-To: <CGME20170322182915eucas1p1e82e604ec8a37d6cd82fdccabe173b87@eucas1p1.samsung.com>
Hi Andrea,
This is updated patch, difference since previous version is following:
- 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.
- current patch is based on
git://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git userfault
branch too, but rebased.
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-03-22 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170322182915eucas1p1e82e604ec8a37d6cd82fdccabe173b87@eucas1p1.samsung.com>
2017-03-22 18:29 ` Alexey Perevalov [this message]
[not found] ` <CGME20170322182918eucas1p204ef2f7aadb0ac41d11f15ef434c74c4@eucas1p2.samsung.com>
2017-03-22 18:29 ` [PATCH v2] userfaultfd: provide pid in userfault msg Alexey Perevalov
2017-03-23 9:42 ` Hillf Danton
2017-03-23 10:07 ` Alexey Perevalov
2017-03-25 11:47 ` Alexey Perevalov
2017-03-27 3:57 ` Hillf Danton
2017-03-29 17:19 ` Andrea Arcangeli
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=1490207346-9703-1-git-send-email-a.perevalov@samsung.com \
--to=a.perevalov@samsung.com \
--cc=aarcange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=i.maximets@samsung.com \
--cc=linux-mm@kvack.org \
/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