From: Peter Xu <peterx@redhat.com>
To: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Mike Rapoport <rppt@kernel.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Kyle Huey <me@kylehuey.com>,
linux-mm@kvack.org, peterx@redhat.com,
Robert O'Callahan <robert@ocallahan.org>,
Suren Baghdasaryan <surenb@google.com>
Subject: [PATCH 2/2] UFFDIO_API.2const: Add an entry for UFFDIO_MOVE
Date: Mon, 12 May 2025 13:19:22 -0400 [thread overview]
Message-ID: <20250512171922.356408-3-peterx@redhat.com> (raw)
In-Reply-To: <20250512171922.356408-1-peterx@redhat.com>
Add the entry for UFFDIO_MOVE in UFFDIO_API.
Signed-off-by: Peter Xu <peterx@redhat.com>
---
man/man2const/UFFDIO_API.2const | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/man/man2const/UFFDIO_API.2const b/man/man2const/UFFDIO_API.2const
index 1c554107a..17ea6f905 100644
--- a/man/man2const/UFFDIO_API.2const
+++ b/man/man2const/UFFDIO_API.2const
@@ -204,6 +204,12 @@ ioctl.
If this feature bit is set,
the write protection faults would be asynchronously resolved
by the kernel.
+.TP
+.BR UFFD_FEATURE_MOVE " (since Linux 6.8)"
+If this feature bit is set,
+the kernel supports resolving faults with the
+.B UFFDIO_MOVE
+ioctl.
.P
The returned
.I argp->ioctls
--
2.49.0
next prev parent reply other threads:[~2025-05-12 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 17:19 [PATCH 0/2] UFFDIO_API.2const: Two man page updates Peter Xu
2025-05-12 17:19 ` [PATCH 1/2] UFFDIO_API.2const: Update userfaultfd handshake and feature probe Peter Xu
2025-05-13 17:54 ` Kyle Huey
2025-05-14 15:59 ` Alejandro Colomar
2025-05-14 17:21 ` Peter Xu
2025-05-14 18:34 ` Alejandro Colomar
2025-05-12 17:19 ` Peter Xu [this message]
2025-05-12 17:34 ` [PATCH 2/2] UFFDIO_API.2const: Add an entry for UFFDIO_MOVE Suren Baghdasaryan
2025-05-14 15:02 ` Alejandro Colomar
2025-05-14 17:22 ` Peter Xu
2025-05-14 18:35 ` 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=20250512171922.356408-3-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=alx@kernel.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=me@kylehuey.com \
--cc=robert@ocallahan.org \
--cc=rppt@kernel.org \
--cc=surenb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.