From: Martin Cracauer <cracauer@cons.org>
To: linux-kernel@vger.kernel.org
Subject: userfaultfd(2) Write Protect / struct uffdio_writeprotect
Date: Sun, 25 Feb 2018 19:00:48 -0500 [thread overview]
Message-ID: <20180226000048.GA40481@cons.org> (raw)
Hoi.
What is the status of the remaining work for userfaultfd(2), the write
protect support? I am talking about 'struct uffdio_writeprotect' and
friends. This helps with my garbage collection work, and there are
virtual machine folks who want to use it for live migration. Right
now I'm using a SIGSEGV handler, nobody wants that.
It is in the aa tree:
git://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git
I think I am missing the commits to master between Sept 7, 2017 and
Sept 20, 2017. Merging from aa to mainline seems to have stopped at
that point.
Anybody knows what the merging status is? I have some free cycles at
this time, however it looks like I'll be taking a full-time job soon.
I'd love to see it in before I get distracted.
More detail:
The write support in userfaultfd(2) helps me with garbage collection.
I was waiting for it to show up in mainline while I was at Google, to
then change SBCL's GC for ITA's search engine QPX to it. That never
happened before I left Google, and I cannot expect testers inside to
run a custom kernel for benchmarking my changes. Tech info is here:
https://www.cons.org/cracauer/cracauer-userfaultfd.html
https://medium.com/@MartinCracauer/generational-garbage-collection-write-barriers-write-protection-and-userfaultfd-2-8b0e796b8f7f
I have not, but can, connect to various virtual machine people to find
out why they aren't complaining about the lack of this. Maybe they
have an alternative that I could use as well?
Anybody else here who has a use case for this?
I'm happy to give more details.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
reply other threads:[~2018-02-26 0:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180226000048.GA40481@cons.org \
--to=cracauer@cons.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).