linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Nadav Amit <namit@vmware.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux-MM <linux-mm@kvack.org>,
	David Hildenbrand <david@redhat.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v3] userfaultfd: provide unmasked address on page-fault
Date: Fri, 4 Mar 2022 10:27:42 +0800	[thread overview]
Message-ID: <YiF5HmWj4DLJKWDV@xz-m1.local> (raw)
In-Reply-To: <F947E5CE-8F1B-498F-83CC-8007F2483155@vmware.com>

On Thu, Mar 03, 2022 at 07:51:26PM +0000, Nadav Amit wrote:
> Peter (et. al),
> 
> I’ll send it in a more orderly fashion later, but let me know if I got
> something completely wrong for the man page change:
> 
> [ Thanks as usual; sorry - limited experience changing man pages ]
> 
> -- >8 --
> 
> From: Nadav Amit <namit@vmware.com>
> Date: Thu, 3 Mar 2022 19:44:37 +0000
> Subject: [PATCH] ioctl_userfaultfd: add UFFD_FEATURE_EXACT_ADDRESS
> 
> Describe the new UFFD_FEATURE_EXACT_ADDRESS API feature.
> 
> Signed-off-by: Nadav Amit <namit@vmware.com>
> ---
>  man2/ioctl_userfaultfd.2 | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
> index 504f61d4b..2d065504e 100644
> --- a/man2/ioctl_userfaultfd.2
> +++ b/man2/ioctl_userfaultfd.2
> @@ -214,6 +214,12 @@ memory accesses to the regions registered with userfaultfd.
>  If this feature bit is set,
>  .I uffd_msg.pagefault.feat.ptid
>  will be set to the faulted thread ID for each page-fault message.
> +.TP
> +.BR UFFD_FEATURE_EXACT_ADDRESS " (since Linux 5.18)"
> +If this feature bit is set,
> +.I uffd_msg.pagefault.address
> +will be set to the exact page-fault address that was reported by the hardware,
> +and will not mask the offset within the page.
>  .PP
>  The returned
>  .I ioctls
> -- 
> 2.25.1

Looks good to me, thanks!

Acked-by: Peter Xu <peterx@redhat.com>

-- 
Peter Xu



  reply	other threads:[~2022-03-04  3:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26  2:26 Nadav Amit
2022-02-26  7:37 ` Mike Rapoport
2022-02-28  9:16 ` Jan Kara
2022-03-03  8:03 ` Peter Xu
2022-03-03 19:05   ` Nadav Amit
2022-03-03 19:51     ` Nadav Amit
2022-03-04  2:27       ` Peter Xu [this message]
2022-03-04 10:38       ` David Hildenbrand
2022-03-07 18:43         ` Nadav Amit
2022-03-04  1:54     ` Andrew Morton

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=YiF5HmWj4DLJKWDV@xz-m1.local \
    --to=peterx@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-mm@kvack.org \
    --cc=namit@vmware.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