linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: mtk.manpages@gmail.com, Andrea Arcangeli <aarcange@redhat.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-man@vger.kernel.org
Subject: Re: [PATCH 2/5] ioctl_userfaultfd.2: describe memory types that can be used from 4.11
Date: Wed, 26 Apr 2017 08:52:50 +0200	[thread overview]
Message-ID: <d22cd916-d9fc-71f7-d451-e4cbd818874c@gmail.com> (raw)
In-Reply-To: <1493137748-32452-3-git-send-email-rppt@linux.vnet.ibm.com>

On 04/25/2017 06:29 PM, Mike Rapoport wrote:
> Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>

Thanks, Mike. Applied.

Cheers,

Michael

> ---
>  man2/ioctl_userfaultfd.2 | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
> index 66fbfdc..78abc4d 100644
> --- a/man2/ioctl_userfaultfd.2
> +++ b/man2/ioctl_userfaultfd.2
> @@ -169,11 +169,15 @@ field was not zero.
>  (Since Linux 4.3.)
>  Register a memory address range with the userfaultfd object.
>  The pages in the range must be "compatible".
> -In the current implementation,
> -.\" According to Mike Rapoport, this will change in Linux 4.11.
> +
> +Up to Linux kernel 4.11,
>  only private anonymous ranges are compatible for registering with
>  .BR UFFDIO_REGISTER .
>  
> +Since Linux 4.11,
> +hugetlbfs and shared memory ranges are also compatible with
> +.BR UFFDIO_REGISTER .
> +
>  The
>  .I argp
>  argument is a pointer to a
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-04-26  6:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 16:29 [PATCH 0/5] {ioctl_}userfaultfd.2: initial updates for 4.11 Mike Rapoport
2017-04-25 16:29 ` [PATCH 1/5] userfaultfd.2: describe memory types that can be used from 4.11 Mike Rapoport
2017-04-26  6:52   ` Michael Kerrisk (man-pages)
2017-04-25 16:29 ` [PATCH 2/5] ioctl_userfaultfd.2: " Mike Rapoport
2017-04-26  6:52   ` Michael Kerrisk (man-pages) [this message]
2017-04-25 16:29 ` [PATCH 3/5] ioctl_userfaultfd.2: update UFFDIO_API description Mike Rapoport
2017-04-25 16:29 ` [PATCH 4/5] userfaultfd.2: add Linux container migration use-case to NOTES Mike Rapoport
2017-04-26  7:16   ` Michael Kerrisk (man-pages)
2017-04-25 16:29 ` [PATCH 5/5] usefaultfd.2: add brief description of "non-cooperative" mode Mike Rapoport
2017-04-26  7:18   ` Michael Kerrisk (man-pages)
2017-04-26  7:23 ` [PATCH 0/5] {ioctl_}userfaultfd.2: initial updates for 4.11 Michael Kerrisk (man-pages)
2017-04-26  7:43   ` Mike Rapoport
2017-04-26  8:43     ` 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=d22cd916-d9fc-71f7-d451-e4cbd818874c@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=aarcange@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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;
as well as URLs for NNTP newsgroup(s).