From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Donnelly Subject: Re: [PATCH 0/7] userfault21 update Date: Mon, 12 Oct 2015 11:04:11 -0400 Message-ID: References: <1434388931-24487-1-git-send-email-aarcange@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Andrew Morton , open list , linux-mm@kvack.org, qemu-devel@nongnu.org, kvm@vger.kernel.org, Pavel Emelyanov , Sanidhya Kashyap , zhang.zhanghailiang@huawei.com, Linus Torvalds , "Kirill A. Shutemov" , Andres Lagar-Cavilla , Dave Hansen , Paolo Bonzini , Rik van Riel , Mel Gorman , Andy Lutomirski , Hugh Dickins , Peter Feiner , "Dr. David Alan Gilbert" , Johannes Weiner , "Huangpeng (Peter)" To: Andrea Arcangeli Return-path: In-Reply-To: <1434388931-24487-1-git-send-email-aarcange@redhat.com> Sender: owner-linux-mm@kvack.org List-Id: kvm.vger.kernel.org Hello Andrea, On Mon, Jun 15, 2015 at 1:22 PM, Andrea Arcangeli wrote: > This is an incremental update to the userfaultfd code in -mm. Sorry I'm late to this party. I'm curious how a ptrace monitor might use a userfaultfd to handle faults in all of its tracees. Is this possible without having each (newly forked) tracee "cooperate" by creating a userfaultfd and passing that to the tracer? Have you considered using one userfaultfd for an entire tree of processes (signaled through a flag)? Would not a process id included in the include/uapi/linux/userfaultfd.h:struct uffd_msg be sufficient to disambiguate faults? -- Patrick Donnelly -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org