From: Peter Xu <peterx@redhat.com>
To: linux-man@vger.kernel.org
Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Nadav Amit <nadav.amit@gmail.com>,
linux-kernel@vger.kernel.org,
Linux MM Mailing List <linux-mm@kvack.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Alejandro Colomar <alx.manpages@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 4/4] ioctl_userfaultfd.2: Add write-protect mode docs
Date: Thu, 4 Mar 2021 11:12:43 -0500 [thread overview]
Message-ID: <20210304161243.GA397383@xz-x1> (raw)
In-Reply-To: <20210304015947.517713-5-peterx@redhat.com>
On Wed, Mar 03, 2021 at 08:59:47PM -0500, Peter Xu wrote:
> Userfaultfd write-protect mode is supported starting from Linux 5.7.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> man2/ioctl_userfaultfd.2 | 74 +++++++++++++++++++++++++++++++++++++---
> 1 file changed, 70 insertions(+), 4 deletions(-)
>
> diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
> index 1965d1932..3feb888a8 100644
> --- a/man2/ioctl_userfaultfd.2
> +++ b/man2/ioctl_userfaultfd.2
> @@ -208,10 +208,11 @@ signal will be sent to the faulting process.
> Applications using this
> feature will not require the use of a userfaultfd monitor for processing
> memory accesses to the regions registered with userfaultfd.
> +.TP
> .BR UFFD_FEATURE_THREAD_ID " (since Linux 4.14)"
> If this feature bit is set,
> .I uffd_msg.pagefault.feat.ptid
> -Will be set
> +will be set to the faulted thread ID for each page fault message.
These two changes should belong to the previous patch - will get them fixed
too.
--
Peter Xu
prev parent reply other threads:[~2021-03-04 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 1:59 [PATCH 0/4] man2: udpate mm/userfaultfd manpages to latest Peter Xu
2021-03-04 1:59 ` [PATCH 1/4] userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-04 6:38 ` Mike Rapoport
2021-03-04 15:53 ` Peter Xu
2021-03-04 9:22 ` Alejandro Colomar (man-pages)
2021-03-04 15:50 ` Peter Xu
2021-03-04 18:13 ` Alejandro Colomar (man-pages)
2021-03-04 1:59 ` [PATCH 2/4] userfaultfd.2: Add write-protect mode Peter Xu
2021-03-04 6:46 ` Mike Rapoport
2021-03-04 16:02 ` Peter Xu
2021-03-04 1:59 ` [PATCH 3/4] ioctl_userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-04 1:59 ` [PATCH 4/4] ioctl_userfaultfd.2: Add write-protect mode docs Peter Xu
2021-03-04 16:12 ` Peter Xu [this message]
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=20210304161243.GA397383@xz-x1 \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alx.manpages@gmail.com \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=nadav.amit@gmail.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