Received: by 10.213.65.68 with SMTP id h4csp426493imn; Tue, 27 Mar 2018 01:49:30 -0700 (PDT) X-Google-Smtp-Source: AG47ELtRln4a+1/Lp8tCEEEiP98ph9KQAqtD+TQGkaZ9GFg9BDyTDZVnfrkUB6if1klocmhouCBi X-Received: by 10.98.247.19 with SMTP id h19mr16076121pfi.239.1522140569886; Tue, 27 Mar 2018 01:49:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522140569; cv=none; d=google.com; s=arc-20160816; b=r+W+jnW6sxCxie4aNJyOZdW7XUupwnoyr5jfX/ut27I1n6rjg1QC6f1u5LGC0uSooF I+GQQih/GSScPobsreih0vjY2o33XPpeTJT8AzR4aDKUpcpk/H+NUFMOPzDBWXeuFt73 JURUlKSGsK8fOmJ4r7sXPu7ZUMM4bqbNRHt9wnLpM6jIEV18MuGuJxnTa71gE3Nzlcug yxBTCf6jGRmWerw+8zrvqG/BF8TomB/AwPD6784YtELXlxV7jEqeY89AIlDZXHZBcveG BwGS2DV6Muup5UT1+eOQACarDhAYlH2vbQDhpZd7Pmx66LHSEevyX5z5mI2ByR0fcqbD WxXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=tn/ZlXEZ88qnDIsbH9NPWX2zfIb+H2E+aRo1sSn4xN4=; b=q/ImA9my45CC+xQZQeXMdPSVzN/BfELSMWfkmt1KDKajZL02+6d+ViqArz4TK4CaOR KAsfjQNui3Lf/YeRgxNu5zrEHGFwNoRhDMDabQ5kasz1PPAkqCK64PGTx2axDhp2zf5A eHfugrbQMToNnOAPYG0Y52r8WLsWX2GMhkTka4I4yDerQN+GrDG6l3QIVN32ZDdg8wtb vYxLMnq+serggOaNzd8dm3+2XJxktf3vNjeRyDH9mwGuOrpto0ovdVtzLpNoxQuEXTe/ 8UEbGGDDBKfsbcpxotAOTxt5cu0yTq4AoO661uwO6sGRfHMnSNlV9nzKy9ARLVDPC6gR QdCg== 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 f62-v6si818909plb.725.2018.03.27.01.49.15; Tue, 27 Mar 2018 01:49:29 -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 S1752201AbeC0Irc (ORCPT + 99 others); Tue, 27 Mar 2018 04:47:32 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:42355 "EHLO huawei.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751020AbeC0Ir0 (ORCPT ); Tue, 27 Mar 2018 04:47:26 -0400 Received: from DGGEMS410-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 81FDAE415AAC4; Tue, 27 Mar 2018 16:47:21 +0800 (CST) Received: from localhost (10.202.226.43) by DGGEMS410-HUB.china.huawei.com (10.3.19.210) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 27 Mar 2018 16:47:13 +0800 Date: Tue, 27 Mar 2018 09:47:01 +0100 From: Jonathan Cameron To: Logan Gunthorpe CC: Bjorn Helgaas , Sinan Kaya , , , , , , , Stephen Bates , Christoph Hellwig , Jens Axboe , Keith Busch , Sagi Grimberg , Bjorn Helgaas , Jason Gunthorpe , Max Gurtovoy , Dan Williams , =?ISO-8859-1?Q?J=E9r=F4me?= Glisse , Benjamin Herrenschmidt , "Alex Williamson" , Eric Wehage Subject: Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory Message-ID: <20180327094701.0000300d@huawei.com> In-Reply-To: References: <20180312193525.2855-1-logang@deltatee.com> <20180312193525.2855-2-logang@deltatee.com> <59fd2f5d-177f-334a-a9c4-0f8a6ec7c303@codeaurora.org> <24d8e5c2-065d-8bde-3f5d-7f158be9c578@deltatee.com> <20180326121138.00005e30@huawei.com> <20180326140118.GA221690@bhelgaas-glaptop.roam.corp.google.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.226.43] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 26 Mar 2018 09:46:24 -0600 Logan Gunthorpe wrote: > On 26/03/18 08:01 AM, Bjorn Helgaas wrote: > > On Mon, Mar 26, 2018 at 12:11:38PM +0100, Jonathan Cameron wrote: > >> On Tue, 13 Mar 2018 10:43:55 -0600 > >> Logan Gunthorpe wrote: > >>> It turns out that root ports that support P2P are far less common than > >>> anyone thought. So it will likely have to be a white list. > >> > >> This came as a bit of a surprise to our PCIe architect. > >> > >> His follow up was whether it was worth raising an ECR for the PCIe spec > >> to add a capability bit to allow this to be discovered. This might > >> long term avoid the need to maintain the white list for new devices. > >> > >> So is it worth having a long term solution for making this discoverable? > > > > It was surprising to me that there's no architected way to discover > > this. It seems like such an obvious thing that I guess I assumed the > > omission was intentional, i.e., maybe there's something that makes it > > impractical, but it would be worth at least asking somebody in the > > SIG. It seems like for root ports in the same root complex, at least, > > there could be a bit somewhere in the root port or the RCRB (which > > Linux doesn't support yet). > > Yes, I agree. It would be a good long term solution to have this bit in > the spec. That would avoid us needing to create a white list for new > hardware. However, I expect it would be years before we can rely on it > so someone may yet implement that white list. > > Logan I'll see if I can get our PCI SIG people to follow this through and see if it is just an omission or as Bjorn suggested, there is some reason we aren't thinking of that makes it hard. Agreed that it is a somewhat tangential question to what to do with current hardware, but let's get the ball rolling if possible. Jonathan