Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp3706936ybx; Mon, 4 Nov 2019 01:25:15 -0800 (PST) X-Google-Smtp-Source: APXvYqy7wgcTFbfIPYXGZmT4FVHRJxVmH3XI8cAhF0X50FGD9kNlKqq3Mz40kxLsMyXEZ2pZYN0I X-Received: by 2002:aa7:d312:: with SMTP id p18mr28067976edq.303.1572859515109; Mon, 04 Nov 2019 01:25:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572859515; cv=none; d=google.com; s=arc-20160816; b=nzHAEf5xo3DwBsc/esZgnSCx3zWYvxdFWdRxAky94qGiW/pNndXbMZ75SX5ArY6hO6 1Q4vof7vVaJjAcOJaW9eLCqpwPWn/v/uSGcHXq8V568MXvm5oHQCvqScWd9a7m/48Fn/ e8FD9ScGJuphlNEx8Ltaw/IiQUsRkPHerBgGLlhFx9KJekEzy9e+Xs8OnPnYWWqshnWs GzH53fj1xNOOajTvx6DmZkCS+otCGQkPKzN00mU8jNDk8XNx/6cOnwZB3k0nsGsOLEdK 9SuOtOFGqizoRiMl+5vWo+8TkU5I86YFJ4r9+AKvcxxcTsMErg+Q2dLMHZxsHZhI3LLA GEhw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject :dkim-signature; bh=1KhMqcfTd19Zfmr/b6DW3CdwxdE3sCVcJ/l2WNDEF7U=; b=N4/5tvTk9L5C9f/+uxUalKYv97GIq72e5tWKMn80YaAPutiBCcQl4cjVA/gk0w783U TA73N23TL9PfdNa6dCGiXOvemN6uPn3uTdsD7Fg96Jgx65TDj3yjSCkpTyZgsnqDWgD3 vE6p9GvpwaOiJKvTWL7U+psKUhA+y/YCXi64GJT6tjMhYb+uLSm8hg14K4E3pyJRjwel nPeCHwd1/l6U1Lexbh1mjg7Pe2J1YFH5QiRMvTV/x0yd7KbFoSQQrKhSRtshW3pIKSKq 5sd4lQXnFx2ABdFSurOzPdvPkKyMPRfbMAxCmXsmCB9nZECqgIXZUVrGj7MGuhkuBfwV eesw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=ByqSth9y; 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 t4si7329094edc.171.2019.11.04.01.24.51; Mon, 04 Nov 2019 01:25:15 -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; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=ByqSth9y; 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 S1728275AbfKDJVv (ORCPT + 99 others); Mon, 4 Nov 2019 04:21:51 -0500 Received: from pio-pvt-msa3.bahnhof.se ([79.136.2.42]:52712 "EHLO pio-pvt-msa3.bahnhof.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727454AbfKDJVu (ORCPT ); Mon, 4 Nov 2019 04:21:50 -0500 Received: from localhost (localhost [127.0.0.1]) by pio-pvt-msa3.bahnhof.se (Postfix) with ESMTP id 108D440666; Mon, 4 Nov 2019 10:21:38 +0100 (CET) Authentication-Results: pio-pvt-msa3.bahnhof.se; dkim=pass (1024-bit key; unprotected) header.d=shipmail.org header.i=@shipmail.org header.b=ByqSth9y; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at bahnhof.se X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=6.31 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from pio-pvt-msa3.bahnhof.se ([127.0.0.1]) by localhost (pio-pvt-msa3.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COSmvI3aZtJa; Mon, 4 Nov 2019 10:21:36 +0100 (CET) Received: from mail1.shipmail.org (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) (Authenticated sender: mb878879) by pio-pvt-msa3.bahnhof.se (Postfix) with ESMTPA id 3C07540663; Mon, 4 Nov 2019 10:21:27 +0100 (CET) Received: from localhost.localdomain (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) by mail1.shipmail.org (Postfix) with ESMTPSA id A001336018B; Mon, 4 Nov 2019 10:21:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=shipmail.org; s=mail; t=1572859286; bh=4xBA0Dni2o2Q85TuTFyQusIiI73YaZ6L+DTBUOzo9Nk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=ByqSth9yKsVbQ72KoftTKl9uWmOfkTVKCreEAYXtN7Hgni/cQP8BlQwxuGzjlOrnk F13EbHuirJq/UVTAKxaWqabLZox/hLxdboH9/IYf/ExR9JmHC2AAmT380Q99t9u4vZ SZHQVViKoQ/H0JgMWgmNBsTvZ+3GdJo06YmOItko= Subject: -mm maintainer? WAS Re: [PATCH v6 0/8] Emulated coherent graphics memory take 2 To: =?UTF-8?Q?Thomas_Hellstr=c3=b6m_=28VMware=29?= , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "torvalds@linux-foundation.org" , "Kirill A . Shutemov" Cc: Andrew Morton , Matthew Wilcox , Will Deacon , Peter Zijlstra , Rik van Riel , Minchan Kim , Michal Hocko , Huang Ying , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= References: <20191014132204.7721-1-thomas_os@shipmail.org> From: =?UTF-8?Q?Thomas_Hellstr=c3=b6m_=28VMware=29?= Organization: VMware Inc. Message-ID: Date: Mon, 4 Nov 2019 10:21:26 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20191014132204.7721-1-thomas_os@shipmail.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, All, On 10/14/19 3:22 PM, Thomas Hellström (VMware) wrote: > From: Thomas Hellström > > Graphics APIs like OpenGL 4.4 and Vulkan require the graphics driver > to provide coherent graphics memory, meaning that the GPU sees any > content written to the coherent memory on the next GPU operation that > touches that memory, and the CPU sees any content written by the GPU > to that memory immediately after any fence object trailing the GPU > operation is signaled. > > Paravirtual drivers that otherwise require explicit synchronization > needs to do this by hooking up dirty tracking to pagefault handlers > and buffer object validation. > > Provide mm helpers needed for this and that also allow for huge pmd- > and pud entries (patch 1-3), and the associated vmwgfx code (patch 4-7). > > The code has been tested and exercised by a tailored version of mesa > where we disable all explicit synchronization and assume graphics memory > is coherent. The performance loss varies of course; a typical number is > around 5%. > > I would like to merge this code through the DRM tree, so an ack to include > the new mm helpers in that merge would be greatly appreciated. > I'm a bit confused as how to get this merged? Is there an -mm maintainer or who is supposed to ack -mm patches and get them into the kernel? Any input appreciated, Thanks, Thomas