public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Nadav Amit <nadav.amit@gmail.com>, linux-man@vger.kernel.org
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	Peter Xu <peterx@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Nadav Amit <namit@vmware.com>
Subject: Re: [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_EXACT_ADDRESS
Date: Fri, 31 Mar 2023 00:52:24 +0200	[thread overview]
Message-ID: <7a4e4c9b-e135-a3bf-17fb-388efd0a341e@gmail.com> (raw)
In-Reply-To: <5281de2a-08c2-e159-0e15-cf4225f4466b@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1623 bytes --]

Hi Nadav,

On 3/14/22 13:23, Alejandro Colomar (man-pages) wrote:
> Hi Nadav,
> 
> On 3/7/22 19:48, Nadav Amit wrote:
>> From: Nadav Amit <namit@vmware.com>
>>
>> Describe the new UFFD_FEATURE_EXACT_ADDRESS API feature.
>>
>> Signed-off-by: Nadav Amit <namit@vmware.com>
>> ---
> 
> LGTM.  Please ping when it's added to Linus's tree,
> and add a comment with the commit message that added it.

I've checked that this was finally added to the kernel.  Should I apply
the patch as is, or is there anything that was changed?

Cheers,

Alex

> 
> Thanks,
> 
> Alex
> 
>>  man2/ioctl_userfaultfd.2 | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
>> index 504f61d4b..94480158e 100644
>> --- a/man2/ioctl_userfaultfd.2
>> +++ b/man2/ioctl_userfaultfd.2
>> @@ -214,6 +214,14 @@ 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.
>> +Note that old Linux versions might indicate the exact address as well,
>> +even though the feature bit is not set.
>>  .PP
>>  The returned
>>  .I ioctls
> 

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-03-30 22:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 18:48 [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_EXACT_ADDRESS Nadav Amit
2022-03-07 18:48 ` [PATCH 2/2] userfaultfd.2: fix userfaultfd_demo output Nadav Amit
2022-03-14 12:28   ` Alejandro Colomar (man-pages)
2023-04-08 13:34   ` Alejandro Colomar
2023-04-10 19:57     ` Nadav Amit
2023-06-02  0:18       ` Alejandro Colomar
2022-03-14 12:23 ` [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_EXACT_ADDRESS Alejandro Colomar (man-pages)
2023-03-30 22:52   ` Alejandro Colomar [this message]
2023-04-04 16:01     ` Nadav Amit
2023-04-08 13:32       ` 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=7a4e4c9b-e135-a3bf-17fb-388efd0a341e@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=david@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=nadav.amit@gmail.com \
    --cc=namit@vmware.com \
    --cc=peterx@redhat.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