Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1896615imu; Thu, 24 Jan 2019 04:00:03 -0800 (PST) X-Google-Smtp-Source: ALg8bN56b+E+xH/y1iELm2RjwhRp4g+3KM//kf4xTjtVQMRNJ18jxcUwhpPf+V2hmZ4Fmxih+3YY X-Received: by 2002:a17:902:d697:: with SMTP id v23mr6169602ply.261.1548331203761; Thu, 24 Jan 2019 04:00:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548331203; cv=none; d=google.com; s=arc-20160816; b=c73VEkrH6xorqNsD6Yv9C/z8ZCH1d5CO5vScQsxNTHvEhaQudtPnnIO6yvZzZ8SSIl XCt7FXhphkP0CmrUZKgWDl6yP/atiDLJ4oARSDtld3nEcHuyKFGNLRMgZzUSyUGWKyFS Tup6XNM1sEZ5FcH+dhCqRa2pXErvD8DLQB45E4NSra9bzXciQdPSuIst7apEO6HP8chb d7F6cNyBJ35ED+43ML1DvTpxHqwVNTdLEK7KaX3P/++/6nYK21ULDsnFzs9PSA8HK8kj 6tHhn2mC8XWAuHt8RTZ+oUPSetLTA44ZeJVbARSiZA0IGFjHkm0Apx7nDef4ELIoAcrf RyZw== 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 :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=VbeioFjoyvHZ0kqOyMn9/cf0HAHLg43hY1KyOPsR8JA=; b=iRAa/ijPelv0FsHgDioOzIjIaGd0HXeCJ2D5xXGB/atoH9gb6s51czl5NwcYLW94jb JcrLYg6o9y2WCv2lXU6/559zdBEueeoYKz4n9bx7hAgDiVg54M30ikOTokP7YyuIasIb m42irnq7Rd8PRMzUOpk6x1Z74b7gh2LJWVnszWZMOeEFAqD7AAo7SoRM6eEAuDg5kWVf 54m5igCYCFcpQdnSZpa8H/woK+rqqZx5k9EL9V/Gocp/qx5MA55lCMaKO22svjAtbnq4 Z40fowpMWufoGP7upVuBF9UuzcBe0fgkNEozqXKhoMRfh7/hY6XUXWdp3FY90VxSubD5 1XGQ== 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 p26si24420644pli.225.2019.01.24.03.59.48; Thu, 24 Jan 2019 04:00:03 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727719AbfAXL7R (ORCPT + 99 others); Thu, 24 Jan 2019 06:59:17 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:2744 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727409AbfAXL7R (ORCPT ); Thu, 24 Jan 2019 06:59:17 -0500 Received: from DGGEMS410-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 321CCF99A6169F84D543; Thu, 24 Jan 2019 19:59:15 +0800 (CST) Received: from localhost (10.206.48.115) by DGGEMS410-HUB.china.huawei.com (10.3.19.210) with Microsoft SMTP Server id 14.3.408.0; Thu, 24 Jan 2019 19:59:14 +0800 Date: Thu, 24 Jan 2019 11:59:02 +0000 From: Jonathan Cameron To: Andrew Donnellan CC: Olof Johansson , Oded Gabbay , "Dave Airlie" , Arnd Bergmann , , Greg Kroah-Hartman , "Linux Kernel Mailing List" , , Subject: Re: [PATCH 00/15] Habana Labs kernel driver Message-ID: <20190124115902.000016cf@huawei.com> In-Reply-To: References: <20190123000057.31477-1-oded.gabbay@gmail.com> Organization: Huawei X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.206.48.115] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 24 Jan 2019 12:03:06 +1100 Andrew Donnellan wrote: > On 24/1/19 8:52 am, Olof Johansson wrote: > > But, I think the largest question I have (for a broader audience) is: > > > > I predict that we will see a handful of these kind of devices over the > > upcoming future -- definitely from ML accelerators but maybe also for > > other kinds of processing, where there's a command-based, buffer-based > > setup sending workloads to an offload engine and getting results back. > > While the first waves will all look different due to design trade-offs > > made in isolation, I think it makes sense to group them in one bucket > > instead of merging them through drivers/misc, if nothing else to > > encourage more cross-collaboration over time. First steps in figuring > > out long-term suitable frameworks is to get a survey of a few > > non-shared implementations. > > > > So, I'd like to propose a drivers/accel drivers subtree, and I'd be > > happy to bootstrap it with a small group (@Dave Airlie: I think your > > input from GPU land be very useful, want to join in?). Individual > > drivers maintained by existing maintainers, of course. > > > > I think it might make sense to move the CAPI/OpenCAPI drivers over as > > well -- not necessarily to change those drivers, but to group them > > with the rest as more show up. > > For cxl/ocxl, I have no objection to moving to this new subtree if > that's what we all agree to do. (what do people do about UAPI headers in > this situation? keep them where they are in misc/?) > > If we do go ahead and set up this new subtree, perhaps we can use the > mailing list I set up at linux-accelerators@lists.ozlabs.org but we > haven't really started using... > Assuming the concensus falls behind this... I'll push this for the CCIX drivers as well as those start to turn up. This particularly driver had passed me by until this email so great to get the heads up via that list! Sounds like a good plan in general to me. Jonathan