Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp4183583img; Tue, 26 Mar 2019 04:49:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqx0RHUDXzE+wejBMXN/FV6RFRGeT5EhKxyytGO06P8bE0r3yGv7PflrYqETWIpz02M8Nkko X-Received: by 2002:a17:902:be18:: with SMTP id r24mr7987121pls.69.1553600980699; Tue, 26 Mar 2019 04:49:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553600980; cv=none; d=google.com; s=arc-20160816; b=hQ5wpBQM3uskR5T/0wjYlwSoHleD+PX7xlkYwYyKoiNJrRV6S0FW74K3qL88A3hzZJ KbabqgYy7eUYGa3kjruHyFiZxzkSrnPBCBPcciwCIx6FGMFVyaFKm3zoVQwi50ruIiz2 1i0ubP6YUoeOV5+CIauK2HAAfdWFTuDGPd9bH6gr1ElvgS9On6Yr+ghmLt8/KDty443v 12s5+l6BTG/5FKhc2Uq/TBe5QORjd9IA0wiwW0CcbNas5yjW0q+o0AjJB6oobVVF/omC Qrr9FjLrWrjVK70Zq/IESdtr/OxjgPhVM9kYiic4yh8nRd9qZwM0H1XQGisdWDSYLvRP Ebvg== 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=yFOMBtZEnUiuHvxTQ6d4LXcPTdpql1j0gCxPrhkr2N0=; b=k7hjc+n1U6fv9AwzONPfqsSh2+c0ACDkdYNDKNp98TStAPd36hJjzSZgU4piAPE9xZ JyIeNkHXfRC/P1raRT6opr01lImmtiaWQmMka4zdkUYHWAg0BBdKsD5s6Q9AndTTDwFM f0YXoyn3G2VCntq9MJm72PGjRPAwgC0eYNoGxbZVvM1Oa77UWiMptHS75VniOaEIjzhP tupd0zQSriR+iPZsopu1lkIc+bqkAoyJt3rt8hK3hnXUoIxKgWzUFb9550vgDncKxacz ZlEFZt8Bdp/TSOyxnX3hbsA7YS0C4SEbnh54R1FtZZJ7QsRdV1MTrpUtNTVG5lPypvrd eW+A== 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 25si9732766pgm.137.2019.03.26.04.49.24; Tue, 26 Mar 2019 04:49:40 -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 S1731374AbfCZLso (ORCPT + 99 others); Tue, 26 Mar 2019 07:48:44 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:35080 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725776AbfCZLsn (ORCPT ); Tue, 26 Mar 2019 07:48:43 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5E5051596; Tue, 26 Mar 2019 04:48:43 -0700 (PDT) Received: from e107981-ln.cambridge.arm.com (e107981-ln.cambridge.arm.com [10.1.197.40]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 07F9F3F59C; Tue, 26 Mar 2019 04:48:41 -0700 (PDT) Date: Tue, 26 Mar 2019 11:48:36 +0000 From: Lorenzo Pieralisi To: Greg KH Cc: Parav Pandit , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, michal.lkml@markovi.net, davem@davemloft.net, jiri@mellanox.com Subject: Re: [RFC net-next 1/8] subdev: Introducing subdev bus Message-ID: <20190326114836.GA4000@e107981-ln.cambridge.arm.com> References: <1551418672-12822-1-git-send-email-parav@mellanox.com> <1551418672-12822-2-git-send-email-parav@mellanox.com> <20190301071727.GA8975@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190301071727.GA8975@kroah.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 01, 2019 at 08:17:27AM +0100, Greg KH wrote: > On Thu, Feb 28, 2019 at 11:37:45PM -0600, Parav Pandit wrote: > > Introduce a new subdev bus which holds sub devices created from a > > primary device. These devices are named as 'subdev'. > > A subdev is identified similarly to pci device using 16-bit vendor id > > and device id. > > Unlike PCI devices, scope of subdev is limited to Linux kernel. > > But these are limited to only PCI devices, right? > > This sounds a lot like that ARM proposal a week or so ago that asked for > something like this, are you working with them to make sure your > proposal works for them as well? (sorry, can't find where that was > announced, it was online somewhere...) Thanks for pointing this out and sorry for the delay in chiming in. Blog post and white paper are available here: https://community.arm.com/developer/ip-products/processors/b/processors-ip-blog/posts/high-performance-device-virtualization-approach-to-standardization It would be certainly good to reach a degree of convergence in this design space, which eventually will be beneficial for the kernel interfaces required. Thanks again for pointing this out. Lorenzo