From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, Peter Xu <peterx@redhat.com>,
linux-man@vger.kernel.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/5] userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs
Date: Mon, 5 Apr 2021 22:01:39 +0200 [thread overview]
Message-ID: <17c949f2-617c-fd71-73df-5a58496ba2c4@gmail.com> (raw)
In-Reply-To: <b733e31a-f149-4d9a-9f08-101c62686b96@gmail.com>
> Thanks. I've applied the patch, but I made a few tweaks afterwards,
> as per the patch below. Notably, I changed "message" to
> "notification", since that seems more consistent with the
> language in the rest of the page. Is it okay, Peter?
Hmmm -- ignore this. For now, I reverted the patch below,
since it causes the following patch to break.
Cheers,
Michael
> diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2
> index 8245253c3..eb2c6d5f9 100644
> --- a/man2/userfaultfd.2
> +++ b/man2/userfaultfd.2
> @@ -78,8 +78,10 @@ all memory ranges that were registered with the object are unregistered
> and unread events are flushed.
> .\"
> .PP
> -Since Linux 4.14, userfaultfd page fault message can selectively embed
> -faulting thread ID information into the fault message.
> +Since Linux 4.14,
> +.\" commit 9d4ac934829ac58c5109c49e6dfe677300e5e652
> +a userfaultfd page fault notification can selectively embed the
> +faulting thread ID information in the notification.
> One needs to enable this feature explicitly using the
> .B UFFD_FEATURE_THREAD_ID
> feature bit when initializing the userfaultfd context.
>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2021-04-05 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 13:13 [PATCH 0/5] Merged patches from others Alejandro Colomar
2021-04-05 13:13 ` [PATCH 1/5] scanf.3: clarify that %n supports type modifiers Alejandro Colomar
2021-04-05 19:48 ` Michael Kerrisk (man-pages)
2021-04-05 13:13 ` [PATCH 2/5] userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Alejandro Colomar
2021-04-05 19:56 ` Michael Kerrisk (man-pages)
2021-04-05 20:01 ` Michael Kerrisk (man-pages) [this message]
2021-04-05 13:13 ` [PATCH 3/5] userfaultfd.2: Add write-protect mode Alejandro Colomar
2021-04-05 21:13 ` Michael Kerrisk (man-pages)
2021-04-06 16:36 ` Peter Xu
2021-04-05 13:13 ` [PATCH 4/5] ioctl_userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Alejandro Colomar
2021-04-05 21:13 ` Michael Kerrisk (man-pages)
2021-04-05 13:13 ` [PATCH 5/5] ioctl_userfaultfd.2: Add write-protect mode docs Alejandro Colomar
2021-04-05 21:14 ` Michael Kerrisk (man-pages)
2021-04-06 8:10 ` [PATCH 0/5] Merged patches from others Michael Kerrisk (man-pages)
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=17c949f2-617c-fd71-73df-5a58496ba2c4@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=peterx@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox