[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230919190206.388896-3-axelrasmussen@google.com>
Date: Tue, 19 Sep 2023 12:01:58 -0700
From: Axel Rasmussen <axelrasmussen@...gle.com>
To: Alejandro Colomar <alx@...nel.org>, Peter Xu <peterx@...hat.com>
Cc: linux-man@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Axel Rasmussen <axelrasmussen@...gle.com>
Subject: [PATCH 02/10] userfaultfd.2: reword to account for new fault
resolution ioctls
Basically, reword the sentence to clarify that this isn't a complete
list. I don't believe it's worth maintaining a fully complete list here,
instead ioctl_userfaultfd.2 is the place to do that. Let this just be an
example.
Signed-off-by: Axel Rasmussen <axelrasmussen@...gle.com>
---
man2/userfaultfd.2 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2
index 1b2af22f9..00d94e514 100644
--- a/man2/userfaultfd.2
+++ b/man2/userfaultfd.2
@@ -222,11 +222,12 @@ operation,
a page fault occurring in the requested memory range, and satisfying
the mode defined at the registration time, will be forwarded by the kernel to
the user-space application.
-The application can then use the
+The application can then use various (e.g.
.B UFFDIO_COPY ,
.B UFFDIO_ZEROPAGE ,
or
.B UFFDIO_CONTINUE
+)
.BR ioctl (2)
operations to resolve the page fault.
.PP
--
2.42.0.459.ge4e396fd5e-goog
Powered by blists - more mailing lists