From: Peter Xu <peterx@redhat.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
linux-mm@kvack.org, Axel Rasmussen <axelrasmussen@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Nadav Amit <nadav.amit@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] userfaultfd.2: Add section for UFFD_USER_MODE_ONLY
Date: Fri, 3 Jun 2022 13:34:19 -0400 [thread overview]
Message-ID: <YppGGxdz7m7vyb85@xz-m1.local> (raw)
In-Reply-To: <ce05bd8d-087d-cfa8-6aca-02fd1f3aebb7@gmail.com>
On Fri, Jun 03, 2022 at 07:11:05PM +0200, Alejandro Colomar wrote:
> Hi Peter,
>
> On 5/31/22 03:11, Peter Xu wrote:
> > Add a paragraph for UFFD_USER_MODE_ONLY flag that was introduced in
> > Linux 5.11.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
>
> See some minor comments below.
>
> Cheers,
>
> Alex
>
> > ---
> > man2/userfaultfd.2 | 14 ++++++++++++--
> > 1 file changed, 12 insertions(+), 2 deletions(-)
> >
> > diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2
> > index cee7c01d2..0928a76d2 100644
> > --- a/man2/userfaultfd.2
> > +++ b/man2/userfaultfd.2
> > @@ -29,8 +29,9 @@
> > userfaultfd \- create a file descriptor for handling page faults in user space
> > .SH SYNOPSIS
> > .nf
> > -.BR "#include <fcntl.h>" " /* Definition of " O_* " constants */"
> > -.BR "#include <sys/syscall.h>" " /* Definition of " SYS_* " constants */"
> > +.BR "#include <fcntl.h>" " /* Definition of " O_* " constants */"
> > +.BR "#include <sys/syscall.h>" " /* Definition of " SYS_* " constants */"
> > +.BR "#include <linux/userfaultfd.h>" " /* Definition of " UFFD_* " constants */"
> > .B #include <unistd.h>
> > .PP
> > .BI "int syscall(SYS_userfaultfd, int " flags );
> > @@ -76,6 +77,15 @@ See the description of the
> > .BR O_NONBLOCK
> > flag in
> > .BR open (2).
> > +.TP
> > +.BR UFFD_USER_MODE_ONLY
>
>
> s/BR/B/
>
> see groff_man(7):
>
> [
> [...]
>
> .B [text]
> Set text in bold. If the macro is given no argu‐
> ments, the text of the next input line is set in
> bold.
>
> [...]
>
> .BR bold‐text roman‐text ...
> Set each argument in bold and roman, alternately.
> ]
>
> > +This is an userfaultfd specific flag that was introduced since Linux 5.11.
> > +When set, the userfaultfd object will only be able to handle page faults
> > +originated from the userspace on the registered regions.
> > +When a kernel originated fault was triggered on the registered range with
> > +this userfaultfd, a
> > +.BR SIGBUS
>
> s/BR/B/
Thanks Alex, I'll fix and repost the patchset soon.
--
Peter Xu
next prev parent reply other threads:[~2022-06-03 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 1:11 [PATCH 0/2] userfaultfd.2: Update to latest Peter Xu
2022-05-31 1:11 ` [PATCH 1/2] userfaultfd.2: Add section for UFFD_USER_MODE_ONLY Peter Xu
2022-06-03 17:11 ` Alejandro Colomar
2022-06-03 17:34 ` Peter Xu [this message]
2022-05-31 1:11 ` [PATCH 2/2] userfaultfd.2: Update on write-protection support Peter Xu
2022-06-03 17:12 ` Alejandro Colomar
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=YppGGxdz7m7vyb85@xz-m1.local \
--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=nadav.amit@gmail.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