Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp3527080pxb; Mon, 16 Nov 2020 17:54:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJwZ+s5XwfdwuxWVU55U9C2NZqq2UBCL2yStMfN2lClTlazXDZ/FEUmv9dRBPs0v2l/Yt0bg X-Received: by 2002:a17:906:3c50:: with SMTP id i16mr17636552ejg.52.1605578065459; Mon, 16 Nov 2020 17:54:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605578065; cv=none; d=google.com; s=arc-20160816; b=0Od1OJEdgvaoxFP/Qb/t4fPP7DeeNftjd8klACLQZHoGo13AIfOY7PfjRGV5/Zl4kY Iuu2itEWWh0d23vKf0lOZ6YkYvb8i+inC7HNa5vOiLc9v5Ir64fcP6NWKNwqm4LXsG4w QHPf6Nx9qB5kXeldRevzNFbTfBC9zhhRJJ8KXx+YTN0yt+f6cN5neruwXkOAvPmygsFV 0u8bDEHC8qBtJZOWd55L6WUkWVWD6WAx4O/HHB3tR7fNkiqz4Ti+L/zKDNrIOlTruBMd 0OreodkEKGpt4cZVtHgYOXDI7EtSVL/+pkqniVG0YKah2IdNyMY/1GfNloHPOQtkyvYb BgTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=hG++UmFKBdKt+ZeTSEb8yBdHSmKCSmHlz7LplY0Rb/Y=; b=uAJcSdHthzIkgWFovJBxgcmc7LIERx/e68jriPscfWufMwFvkM1NUAI4yh3rdky8qN HjbgcR6X/6xGUvFP5iJ5dTJ7TY/LUM2lqTHEWB/5Nva237e36pvFWvn3C4g5aPT+8B3S C9dJOLLMNg5y1Lutiz1lYnLVfsEELifWByBz7QZ1pJd1BLwW9W94AXYsL0MpjuyyQGDU +/ZrCqpLVMvccsTeRyDTdVeaY9E7siuuA4fHAz5ns4LgDWxEnlHM4g5MjUf5Z7dmsu81 koYv7R3xkgj870MkFtQkCrqxE57wma2rB2DLt8cYK078x6QjhTGJfMqfbfhpH9JyKJ2C 7aBg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o536oL+2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id qu17si12147146ejb.266.2020.11.16.17.54.02; Mon, 16 Nov 2020 17:54:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o536oL+2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731180AbgKPPhY (ORCPT + 99 others); Mon, 16 Nov 2020 10:37:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:57200 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730415AbgKPPhX (ORCPT ); Mon, 16 Nov 2020 10:37:23 -0500 Received: from mail-oo1-f41.google.com (mail-oo1-f41.google.com [209.85.161.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B2B9522265; Mon, 16 Nov 2020 15:37:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605541042; bh=E8sdLeoXIzuGmOa5OnMrHgj2yXn2UCzO0W2afC9rPuk=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=o536oL+2jBT8rxRsfC+tXAjv5gHqLzcLVB31sbOHhgsVNlS+Geq0O1pZzwyVYAlX4 GcZhqkXekHID+qw9bCtRwibJo7SFgfT6j9ItPu+Fa1fhCIF5rtMtt7ew3966SBrfZm m5K3fr6EQlAfSWBq4AZpKRR5x+KLsMvCxrsC9Ots= Received: by mail-oo1-f41.google.com with SMTP id l10so3989210oom.6; Mon, 16 Nov 2020 07:37:22 -0800 (PST) X-Gm-Message-State: AOAM531TRRKbqJjhGfBD9H0VB0Ksuk0lNNuP9cISV0ejm7vWjTjyKjMm SqnQvXEnG3ZQbVHavpnusNzh9qudSMII0mUPVZM= X-Received: by 2002:a4a:a217:: with SMTP id m23mr10462852ool.26.1605541041921; Mon, 16 Nov 2020 07:37:21 -0800 (PST) MIME-Version: 1.0 References: <20200930153519.7282-16-kishon@ti.com> <30c8f7a1-baa5-1eb4-d2c2-9a13be896f0f@ti.com> <5a9115c8-322e-ffd4-6274-ae98c375b21d@ti.com> In-Reply-To: From: Arnd Bergmann Date: Mon, 16 Nov 2020 16:37:05 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 15/18] NTB: Add support for EPF PCI-Express Non-Transparent Bridge To: Kishon Vijay Abraham I Cc: Sherry Sun , "bhelgaas@google.com" , Jonathan Corbet , "lorenzo.pieralisi@arm.com" , "arnd@arndb.de" , "jdmason@kudzu.us" , "dave.jiang@intel.com" , "allenbh@gmail.com" , "tjoseph@cadence.com" , Rob Herring , "gregkh@linuxfoundation.org" , "linux-pci@vger.kernel.org" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-ntb@googlegroups.com" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 16, 2020 at 6:19 AM Kishon Vijay Abraham I wrote: > On 12/11/20 6:54 pm, Arnd Bergmann wrote: > > > > This looks very promising indeed, I need to read up on the whole > > discussion there. I also see your slides at [1] that help do explain some > > of it. I have one fundamental question that I can't figure out from > > the description, maybe you can help me here: > > > > How is the configuration managed, taking the EP case as an > > example? Your UseCase1 example sounds like the system that owns > > the EP hardware is the one that turns the EP into a vhost device, > > and creates a vhost-rpmsg device on top, while the RC side would > > probe the pci-vhost and then detect a virtio-rpmsg device to talk to. > > That's correct. Slide no 9 in [1] should give the layering details. > > > Can it also do the opposite, so you end up with e.g. a virtio-net > > device on the EP side and vhost-net on the RC? > > Unfortunately no. Again referring slide 9 in [1], we only have > vhost-pci-epf on the EP side which only creates a "vhost_dev" to deal > with vhost side of things. For doing the opposite, we'd need to create > virtio-pci-epf for EP side that interacts with core virtio (and also the > corresponding vhost back end on PCI host). Ok, I see. So I think this is the opposite of drivers/misc/mic and the bluefield driver were using, so we would probably end up needing both. Then again, I guess the NTB driver would give us the functionality for free, if it shows a symmetric link? Arnd