Received: by 10.223.185.116 with SMTP id b49csp3185933wrg; Sun, 25 Feb 2018 16:18:00 -0800 (PST) X-Google-Smtp-Source: AH8x227DnHOhoPrM0RaTZpW+mbZaU47nUJt6qoztL54JzGI820lWJg3IGnK4nJWRkEk80fqwqbvE X-Received: by 10.99.116.70 with SMTP id e6mr6937792pgn.256.1519604280057; Sun, 25 Feb 2018 16:18:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519604280; cv=none; d=google.com; s=arc-20160816; b=lG6u8R0aeixlGCeJDoxlhLn2AMUIQrCtcS300wqxw6wzB06MkvIJHSaMq288NTcELj 0zoSBpOHkWJVPNFrtYV6i/tyJyh7u42Ml251uAhZh944Xut1cBeHCz4ueIlWoQyqIp0B K1x09u8F66vgL1tWtkw5rj57feuVRk73zlJ5SqY7KdVbH18/gmyJjR9cJxO06n1JRVY/ kmkMkwuVPNg1lHw/3ZrWHR+HLn8HnSHmpj09R0a507P80XZaEApCJpGPbEZBmAGs0r57 O02zhqBmLZkzDDd+HE9u+I0Ael0mMQ6TXKIZA7qF0ADWjnKC58atGQ/hGSRIp2WZ0zmd 5nXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:to:from:date :arc-authentication-results; bh=1PDkp8E2klDd9m/oGyNKhTaG23X4ZpWb/qPhnLNuh78=; b=a03x+GjyCK8UUuTRsPJhvl4uuAvtPQGSThYsz7crAbWoD5SCUOo6oOc2aAiFiD7OpA a0rPa5loObvOz2gPpsrL1OyU8Gw/fhT9U8T76NJllqyPb12Gw/Ne/1BtZZPnfAj6i9cH saB9PzWon1ubVHtn1yYSXfpkeAd/ts5RZvmL72XSyMJKlQjL20hF8PAYSvv2XX9EplvP WDenk1ZtDlKZi0GejoFwYWfXoPLLwa3LOxxq1qimbrT2bArKH1g7DyETB04V6BSF7+IZ G1gPpGa6ODdLjs7MR+qe1hevv4dbZa2fOjS44RQFk5pAyAeXJ5qVxyegwDCXkvJt+0uN Wkkw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g12-v6si5768522pla.564.2018.02.25.16.17.34; Sun, 25 Feb 2018 16:18:00 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751934AbeBZAQf (ORCPT + 99 others); Sun, 25 Feb 2018 19:16:35 -0500 Received: from koef.zs64.net ([212.12.50.230]:34337 "EHLO koef.zs64.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751817AbeBZAQd (ORCPT ); Sun, 25 Feb 2018 19:16:33 -0500 X-Greylist: delayed 943 seconds by postgrey-1.27 at vger.kernel.org; Sun, 25 Feb 2018 19:16:32 EST Received: from koef.zs64.net (koef.zs64.net [IPv6:2a00:14b0:4200:32e0:0:0:0:1e6]) by koef.zs64.net (8.15.2/8.15.2) with ESMTP id w1Q00mhF053276 for ; Mon, 26 Feb 2018 00:00:48 GMT (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.15.2/8.15.2/Submit) id w1Q00mY5053275 for linux-kernel@vger.kernel.org; Sun, 25 Feb 2018 19:00:48 -0500 (EST) (envelope-from cracauer) Date: Sun, 25 Feb 2018 19:00:48 -0500 From: Martin Cracauer To: linux-kernel@vger.kernel.org Subject: userfaultfd(2) Write Protect / struct uffdio_writeprotect Message-ID: <20180226000048.GA40481@cons.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 http://www.cons.org/cracauer/