From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38CF3C4363A for ; Tue, 20 Oct 2020 20:08:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C07E8206FB for ; Tue, 20 Oct 2020 20:08:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2409364AbgJTUIq (ORCPT ); Tue, 20 Oct 2020 16:08:46 -0400 Received: from mga17.intel.com ([192.55.52.151]:7666 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2409351AbgJTUIq (ORCPT ); Tue, 20 Oct 2020 16:08:46 -0400 IronPort-SDR: iVIZITtAsyuqjuXbmE+f79Tfsq04DpIjm6U8oRBErwyxl0aK1aVICGXDekCDL4AFqI0VpRmR3Z ABEmSsBuTFrg== X-IronPort-AV: E=McAfee;i="6000,8403,9780"; a="147127037" X-IronPort-AV: E=Sophos;i="5.77,398,1596524400"; d="scan'208";a="147127037" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Oct 2020 13:08:46 -0700 IronPort-SDR: X2xMZhMuI0ydwzsEmz/J1WmGU/O2RF0S0yJ+fd1pC7zS0/r2uuekxjUQ/xPClehnEqwu19H2Ib jnjlrHz/rNMw== X-IronPort-AV: E=Sophos;i="5.77,398,1596524400"; d="scan'208";a="316140102" Received: from otc-nc-03.jf.intel.com (HELO otc-nc-03) ([10.54.39.36]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Oct 2020 13:08:45 -0700 Date: Tue, 20 Oct 2020 13:08:44 -0700 From: "Raj, Ashok" To: Jason Gunthorpe Cc: "Liu, Yi L" , "Tian, Kevin" , Jason Wang , "alex.williamson@redhat.com" , "eric.auger@redhat.com" , "baolu.lu@linux.intel.com" , "joro@8bytes.org" , "jacob.jun.pan@linux.intel.com" , "Tian, Jun J" , "Sun, Yi Y" , "jean-philippe@linaro.org" , "peterx@redhat.com" , "Wu, Hao" , "stefanha@gmail.com" , "iommu@lists.linux-foundation.org" , "kvm@vger.kernel.org" , "Michael S. Tsirkin" , "Zhu, Lingshan" , Ashok Raj Subject: Re: (proposal) RE: [PATCH v7 00/16] vfio: expose virtual Shared Virtual Addressing to VMs Message-ID: <20201020200844.GC86371@otc-nc-03> References: <20201016153632.GM6219@nvidia.com> <20201019142526.GJ6219@nvidia.com> <20201020140217.GI6219@nvidia.com> <20201020162430.GA85321@otc-nc-03> <20201020170336.GK6219@nvidia.com> <20201020195146.GA86371@otc-nc-03> <20201020195557.GO6219@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201020195557.GO6219@nvidia.com> User-Agent: Mutt/1.5.24 (2015-08-30) Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, Oct 20, 2020 at 04:55:57PM -0300, Jason Gunthorpe wrote: > On Tue, Oct 20, 2020 at 12:51:46PM -0700, Raj, Ashok wrote: > > I think we agreed (or agree to disagree and commit) for device types that > > we have for SIOV, VFIO based approach works well without having to re-invent > > another way to do the same things. Not looking for a shortcut by any means, > > but we need to plan around existing hardware though. Looks like vDPA took > > some shortcuts then to not abstract iommu uAPI instead :-)? When all > > necessary hardware was available.. This would be a solved puzzle. > > I think it is the opposite, vIOMMU and related has outgrown VFIO as > the "home" and needs to stand alone. > > Apparently the HW that will need PASID for vDPA is Intel HW, so if So just to make this clear, I did check internally if there are any plans for vDPA + SVM. There are none at the moment. It seems like you have better insight into our plans ;-). Please do let me know who confirmed vDPA roadmap with you and I would love to talk to them to clear the air. Cheers, Ashok From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2AABFC4363A for ; Tue, 20 Oct 2020 20:08:51 +0000 (UTC) Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8C3412225D for ; Tue, 20 Oct 2020 20:08:50 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8C3412225D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by fraxinus.osuosl.org (Postfix) with ESMTP id 05A8285008; Tue, 20 Oct 2020 20:08:50 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from fraxinus.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RwgVRv5db3XX; Tue, 20 Oct 2020 20:08:48 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [140.211.9.56]) by fraxinus.osuosl.org (Postfix) with ESMTP id C1C0C84B1F; Tue, 20 Oct 2020 20:08:48 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id A35BDC088B; Tue, 20 Oct 2020 20:08:48 +0000 (UTC) Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 504C1C0051 for ; Tue, 20 Oct 2020 20:08:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id 3E8F7873EF for ; Tue, 20 Oct 2020 20:08:47 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q7lvBnZaWoS4 for ; Tue, 20 Oct 2020 20:08:46 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by hemlock.osuosl.org (Postfix) with ESMTPS id 7FE33873DA for ; Tue, 20 Oct 2020 20:08:46 +0000 (UTC) IronPort-SDR: IzyLNe4bk9Qrxi2BWZGkICBMP+M0cLAuCzPI0qORhisAYEL5F4QfuYT12bD3E+2IEzGg28YJ0I v7ZwQq4F0Jig== X-IronPort-AV: E=McAfee;i="6000,8403,9780"; a="231465742" X-IronPort-AV: E=Sophos;i="5.77,398,1596524400"; d="scan'208";a="231465742" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Oct 2020 13:08:45 -0700 IronPort-SDR: X2xMZhMuI0ydwzsEmz/J1WmGU/O2RF0S0yJ+fd1pC7zS0/r2uuekxjUQ/xPClehnEqwu19H2Ib jnjlrHz/rNMw== X-IronPort-AV: E=Sophos;i="5.77,398,1596524400"; d="scan'208";a="316140102" Received: from otc-nc-03.jf.intel.com (HELO otc-nc-03) ([10.54.39.36]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Oct 2020 13:08:45 -0700 Date: Tue, 20 Oct 2020 13:08:44 -0700 From: "Raj, Ashok" To: Jason Gunthorpe Subject: Re: (proposal) RE: [PATCH v7 00/16] vfio: expose virtual Shared Virtual Addressing to VMs Message-ID: <20201020200844.GC86371@otc-nc-03> References: <20201016153632.GM6219@nvidia.com> <20201019142526.GJ6219@nvidia.com> <20201020140217.GI6219@nvidia.com> <20201020162430.GA85321@otc-nc-03> <20201020170336.GK6219@nvidia.com> <20201020195146.GA86371@otc-nc-03> <20201020195557.GO6219@nvidia.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201020195557.GO6219@nvidia.com> User-Agent: Mutt/1.5.24 (2015-08-30) Cc: "Tian, Jun J" , "Tian, Kevin" , Ashok Raj , "kvm@vger.kernel.org" , "jean-philippe@linaro.org" , "stefanha@gmail.com" , Jason Wang , "Michael S. Tsirkin" , "Sun, Yi Y" , "iommu@lists.linux-foundation.org" , "alex.williamson@redhat.com" , "Zhu, Lingshan" , "Wu, Hao" X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: iommu-bounces@lists.linux-foundation.org Sender: "iommu" On Tue, Oct 20, 2020 at 04:55:57PM -0300, Jason Gunthorpe wrote: > On Tue, Oct 20, 2020 at 12:51:46PM -0700, Raj, Ashok wrote: > > I think we agreed (or agree to disagree and commit) for device types that > > we have for SIOV, VFIO based approach works well without having to re-invent > > another way to do the same things. Not looking for a shortcut by any means, > > but we need to plan around existing hardware though. Looks like vDPA took > > some shortcuts then to not abstract iommu uAPI instead :-)? When all > > necessary hardware was available.. This would be a solved puzzle. > > I think it is the opposite, vIOMMU and related has outgrown VFIO as > the "home" and needs to stand alone. > > Apparently the HW that will need PASID for vDPA is Intel HW, so if So just to make this clear, I did check internally if there are any plans for vDPA + SVM. There are none at the moment. It seems like you have better insight into our plans ;-). Please do let me know who confirmed vDPA roadmap with you and I would love to talk to them to clear the air. Cheers, Ashok _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu