Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp3645363ybd; Tue, 25 Jun 2019 06:14:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqxOJKcvcp+tTuWXjYyOq+EZz+DmR/o1VkG89aMB6zDXTo0bIu1nyLOnsdk8cHvBlNdU+XQY X-Received: by 2002:a63:c006:: with SMTP id h6mr37961188pgg.285.1561468463400; Tue, 25 Jun 2019 06:14:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561468463; cv=none; d=google.com; s=arc-20160816; b=nXD6wemVAN2muugFTMgN03bt9mP8g2Qz1FPO+KYBXM42M0sdqsyNwJ3KsbHW37+xA3 CCh1uGnnnWYuXDWrfXB/J89NRmAY3idiBwBdpi3xglsmaxV6X/DupNo5eq8mb93R5Bg5 Qk25AMNLNDN6OUvqZ/lGo7dP8YgJvmwmEEKwcHJ2Rey0K6QXvW96kepwhbbdFdV6hyyf yAe6UoyPNsDdnstn3i7n/ePiDiLKQvDW4xf3IPNyrFt9y4K5MoNG2IczVDeeIFt46DWV g/sm1Uj2UGzw/IXT0I6coFUAM3H/3RF3s13qmwaqW6J23sO6mHQeF1vopfQ59tkC/8Bs dSbA== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=lE+7liccnRpiIpgLdMxWmMKoiV3j2oVjRzHS5uLvmvY=; b=1J7bcmLpwnVb12S2ubtOhJk79JRm4E50ptX27NEyDpYgEzAuQ025lApGL6Igakonsr VjNr9dou4zqGNaVbCHiBimjIF7Ai5TrB0SSSx5/d22BE0m0es5qvFgAuNdtZXnfOujG2 tfuB7XD+zb2jvMtz+jZeGvPNerFaNadUo86r4xm/yllIHhPkp85zKELGzqpBhzY0wjxq i0mtAZU8AxKhCO+dEtRgV9p3rwUEC8+xjOVUYplQ0yTDNZ60xOJpCfm184JIDvnD4rk7 CPKp55vXXtHyI0qkiikICXAFLwQwreM/MpAN+JjlOM+3anIjUmO8tV1U1KWLAN+b7LTM Hipw== 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 62si349672plb.258.2019.06.25.06.14.07; Tue, 25 Jun 2019 06:14:23 -0700 (PDT) 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 S1727775AbfFYL7y (ORCPT + 99 others); Tue, 25 Jun 2019 07:59:54 -0400 Received: from verein.lst.de ([213.95.11.211]:34177 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726423AbfFYL7y (ORCPT ); Tue, 25 Jun 2019 07:59:54 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id D3FF468B05; Tue, 25 Jun 2019 13:59:21 +0200 (CEST) Date: Tue, 25 Jun 2019 13:59:21 +0200 From: Christoph Hellwig To: Jason Gunthorpe Cc: Christoph Hellwig , Michal Hocko , Dan Williams , =?iso-8859-1?B?Suly9G1l?= Glisse , Ben Skeggs , "linux-mm@kvack.org" , "nouveau@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" , "linux-nvdimm@lists.01.org" , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 18/22] mm: mark DEVICE_PUBLIC as broken Message-ID: <20190625115921.GA3874@lst.de> References: <20190613094326.24093-1-hch@lst.de> <20190613094326.24093-19-hch@lst.de> <20190620192648.GI12083@dhcp22.suse.cz> <20190625072915.GD30350@lst.de> <20190625114422.GA3118@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190625114422.GA3118@mellanox.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 25, 2019 at 11:44:28AM +0000, Jason Gunthorpe wrote: > Which tree and what does the resolution look like? Looks like in -mm. The current commit in linux-next is: commit 0d23b042f26955fb35721817beb98ba7f1d9ed9f Author: Robin Murphy Date: Fri Jun 14 10:42:14 2019 +1000 mm: clean up is_device_*_page() definitions > Also, I don't want to be making the decision if we should keep/remove > DEVICE_PUBLIC, so let's get an Ack from Andrew/etc? > > My main reluctance is that I know there is HW out there that can do > coherent, and I want to believe they are coming with patches, just > too slowly. But I'd also rather those people defend themselves :P Lets keep everything as-is for now. I'm pretty certain nothing will show up, but letting this linger another release or two shouldn't be much of a problem. And if we urgently feel like removing it we can do it after -rc1.