Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965328AbbEMOwW (ORCPT ); Wed, 13 May 2015 10:52:22 -0400 Received: from mx2.parallels.com ([199.115.105.18]:47427 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934074AbbEMOwU (ORCPT ); Wed, 13 May 2015 10:52:20 -0400 Message-ID: <5553651B.1020909@parallels.com> Date: Wed, 13 May 2015 17:52:11 +0300 From: Pavel Emelyanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Andrea Arcangeli CC: Linux Kernel Mailing List , Linux MM , Sanidhya Kashyap Subject: [PATCH 0/5] UserfaultFD: Extension for non cooperative uffd usage (v2) Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: US-EXCH2.sw.swsoft.com (10.255.249.46) To US-EXCH2.sw.swsoft.com (10.255.249.46) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 949 Lines: 26 Hi, This set is to address the issues that appear in userfaultfd usage scenarios when the task monitoring the uffd and the mm-owner do not cooperate to each other on VM changes such as remaps, madvises and fork()-s. This is the re-based set on the recent userfaultfd branch, two major changes are: * No need in separate API version, the uffd_msg introduced in the current code and UFFD_API ioctl are enough for the needed extentions * Two events added -- for mremap() and madvise() MADV_DONTNEED More details about the particular events are in patches 3 trough 4. Comments and suggestion are warmly welcome :) The v1 discussion thread is here: https://lkml.org/lkml/2015/3/18/729 Thanks, Pavel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/