linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hugh Dickins <hughd@google.com>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH v2] ioctl_userfaultfd.2, userfaultfd.2: add minor fault mode
Date: Tue, 27 Jul 2021 12:37:28 -0400	[thread overview]
Message-ID: <YQA2SC4ecPh7cz7f@t490s> (raw)
In-Reply-To: <20210604195622.1249588-1-axelrasmussen@google.com>

On Fri, Jun 04, 2021 at 12:56:22PM -0700, Axel Rasmussen wrote:
> Userfaultfd minor fault mode is supported starting from Linux 5.13.
> 
> This commit adds a description of the new mode, as well as the new ioctl
> used to resolve such faults. The two go hand-in-hand: one can't resolve
> a minor fault without continue, and continue can't be used to resolve
> any other kind of fault.
> 
> This patch covers just the hugetlbfs implementation (in 5.13). Support
> for shmem is forthcoming, but as it has not yet made it into a kernel
> release candidate, it will be added in a future commit.
> 
> Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>

FWIW:

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

-- 
Peter Xu


      parent reply	other threads:[~2021-07-27 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 19:56 [PATCH v2] ioctl_userfaultfd.2, userfaultfd.2: add minor fault mode Axel Rasmussen
2021-07-27 16:32 ` Axel Rasmussen
2021-08-02 11:21   ` Mike Rapoport
2021-08-02 12:21     ` Alejandro Colomar (man-pages)
2022-03-22 16:31       ` Axel Rasmussen
2022-04-02 21:48         ` Alejandro Colomar (man-pages)
2021-07-27 16:37 ` 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=YQA2SC4ecPh7cz7f@t490s \
    --to=peterx@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.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).