From: Peter Xu <peterx@redhat.com>
To: Kyle Huey <me@kylehuey.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, criu@lists.linux.dev,
Robert O'Callahan <robert@ocallahan.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Mike Rapoport <rppt@kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: Suppress pte soft-dirty bit with UFFDIO_COPY?
Date: Tue, 13 May 2025 09:24:58 -0400 [thread overview]
Message-ID: <aCNIKm5OJ2h12z2j@x1.local> (raw)
In-Reply-To: <CAP045Ao-onmzcVSic+4D+aDc_M9HTF7UK3NAdC5BcZvDmN370g@mail.gmail.com>
On Mon, May 12, 2025 at 10:16:12AM -0700, Kyle Huey wrote:
> Personally I don't think it's a real issue to have to create a
> sacrificial fd once at process initialization to see what features are
> available. I wouldn't have even said anything if the man page hadn't
> explicitly told me there was another way.
Yes, that's indeed the part that could be confusing and needs fixing. Just
to keep a record (I have you copied), I sent the man-pages changes here:
https://lore.kernel.org/r/20250512171922.356408-1-peterx@redhat.com
We can stick with the sacrificial fd until there's a solid clue showing
that we should introduce a new way to probe.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2025-05-13 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 16:37 Kyle Huey
2025-05-05 20:05 ` Peter Xu
2025-05-05 22:15 ` Kyle Huey
2025-05-12 3:06 ` Kyle Huey
2025-05-12 15:54 ` Peter Xu
2025-05-12 17:16 ` Kyle Huey
2025-05-13 13:24 ` Peter Xu [this message]
2025-05-23 20:32 ` Axel Rasmussen
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=aCNIKm5OJ2h12z2j@x1.local \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=criu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=me@kylehuey.com \
--cc=robert@ocallahan.org \
--cc=rppt@kernel.org \
/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