Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp5244589imb; Thu, 7 Mar 2019 10:57:14 -0800 (PST) X-Google-Smtp-Source: APXvYqxdiFzX8eS97i/4dT78XPXHhXjXSNs9XcLDw8VEjqLaVA8YFkG6cZ2ujE4asKYOIeR5IOKj X-Received: by 2002:a17:902:8609:: with SMTP id f9mr14396604plo.85.1551985034801; Thu, 07 Mar 2019 10:57:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551985034; cv=none; d=google.com; s=arc-20160816; b=APmJeXGkeJbqV114j8S8DNq8uaNHf3PzB5PLmpG04Sz9XWxnSefaZWorQ4/oh5e35A NML25q3efDhELXZjrVnNYhffePH2EFC+hkF1oFljyfWzJleW7JBy++/Q5/64Dv+2ypTe CW3qnA7rm+J4WXQv4R5nV1dm9zMJpjsJXyU4p+LkgNVS1mBoFNIsUZwEzULgFilrdDjd CRTDOCW5JlnVYFfsO4wuXI6dt27tKyrq5heiXlbKS1UY0LRP3XxilHa7RjMSZ8Y/BP0k /NYyVmqwCZ47oItjwPksKg4CL6GcBe/hEr24kH7B+kez3icnHDGecruVVbxRlKLYtp6Q NPWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=7g6R7arc9MO4XHg9VJeEmN4q7bHX3l4uTM+2nxIkx3o=; b=pjMoBcCzQLc3Ir2Xhya2hpIheQrYbR1GPmfqAoWUtPsAFCe4mHmOYj6kCKhCxfeeb/ hNS+N4sXSQqnIX3NEuLuTx59BgPqSPOzXhPiQBxyNEdRli468N83R9L9J1A5RB1ESs/A qy8F3cKDKM6yluWQFqpBICLnvNLTG0ZA4X7j+Q1T84aF2P6b8KctJOSi30sBlalNewXb 22d+P/bnlPsdyAzAov2bYRuBYXkzDgmaFt/bpne59rIzx5Ouc/3a86EoM1SkGfuw4tR8 kfvgWDMn2bP+Rqcs+vOaucOYQg7MW54/idCssDwGm+uds4vE/dB8IGi9+h52etzFvO4k h8/g== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q63si5134058pfb.154.2019.03.07.10.56.59; Thu, 07 Mar 2019 10:57:14 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726392AbfCGS41 (ORCPT + 99 others); Thu, 7 Mar 2019 13:56:27 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42554 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726248AbfCGS41 (ORCPT ); Thu, 7 Mar 2019 13:56:27 -0500 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A060F30917A8; Thu, 7 Mar 2019 18:56:26 +0000 (UTC) Received: from redhat.com (ovpn-125-54.rdu2.redhat.com [10.10.125.54]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A2D7F19C65; Thu, 7 Mar 2019 18:56:25 +0000 (UTC) Date: Thu, 7 Mar 2019 13:56:23 -0500 From: Jerome Glisse To: Andrew Morton Cc: Dan Williams , Linux MM , Linux Kernel Mailing List , Ralph Campbell , John Hubbard , linux-fsdevel Subject: Re: [PATCH 09/10] mm/hmm: allow to mirror vma of a file on a DAX backed filesystem Message-ID: <20190307185623.GD3835@redhat.com> References: <20190130030317.GC10462@redhat.com> <20190130183616.GB5061@redhat.com> <20190131041641.GK5061@redhat.com> <20190305141635.8134e310ba7187bc39532cd3@linux-foundation.org> <20190307094654.35391e0066396b204d133927@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190307094654.35391e0066396b204d133927@linux-foundation.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.41]); Thu, 07 Mar 2019 18:56:26 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 07, 2019 at 09:46:54AM -0800, Andrew Morton wrote: > On Tue, 5 Mar 2019 20:20:10 -0800 Dan Williams wrote: > > > My hesitation would be drastically reduced if there was a plan to > > avoid dangling unconsumed symbols and functionality. Specifically one > > or more of the following suggestions: > > > > * EXPORT_SYMBOL_GPL on all exports to avoid a growing liability > > surface for out-of-tree consumers to come grumble at us when we > > continue to refactor the kernel as we are wont to do. > > The existing patches use EXPORT_SYMBOL() so that's a sticking point. > Jerome, what would happen is we made these EXPORT_SYMBOL_GPL()? So Dan argue that GPL export solve the problem of out of tree user and my personnal experience is that it does not. The GPU sub-system has tons of GPL drivers that are not upstream and we never felt that we were bound to support them in anyway. We always were very clear that if you are not upstream that you do not have any voice on changes we do. So my exeperience is that GPL does not help here. It is just about being clear and ignoring anyone who does not have an upstream driver ie we have free hands to update HMM in anyway as long as we keep supporting the upstream user. That being said if the GPL aspect is that much important to some then fine let switch all HMM symbol to GPL. > > > * A commitment to consume newly exported symbols in the same merge > > window, or the following merge window. When that goal is missed revert > > the functionality until such time that it can be consumed, or > > otherwise abandoned. > > It sounds like we can tick this box. I wouldn't be too strick either, when adding something in release N the driver change in N+1 can miss N+1 because of bug or regression and be push to N+2. I think a better stance here is that if we do not get any sign-off on the feature from driver maintainer for which the feature is intended then we just do not merge. If after few release we still can not get the driver to use it then we revert. It just feels dumb to revert at N+1 just to get it back in N+2 as the driver bit get fix. > > > * No new symbol exports and functionality while existing symbols go unconsumed. > > Unsure about this one? With nouveau upstream now everything is use. ODP will use some of the symbol too. PPC has patchset posted to use lot of HMM too. I have been working with other vendor that have patchset being work on to use HMM too. I have not done all those function just for the fun of it :) They do have real use and user. It took a longtime to get nouveau because of userspace we had a lot of catchup to do in mesa and llvm and we are still very rough there. Cheers, J?r?me