From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 37D46A04BA; Mon, 5 Oct 2020 11:56:50 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 95C652B9C; Mon, 5 Oct 2020 11:56:48 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id BA6E11B3C8 for ; Mon, 5 Oct 2020 11:56:46 +0200 (CEST) IronPort-SDR: 63T5Co9e05XOOngzZBlHkWRBMo39xL9ZUnjtJdDaprJcYelDa/v57zHW3JaeGpwqevY/KbV9OY 9pwL/2rKJDEw== X-IronPort-AV: E=McAfee;i="6000,8403,9764"; a="181488656" X-IronPort-AV: E=Sophos;i="5.77,338,1596524400"; d="scan'208";a="181488656" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Oct 2020 02:56:42 -0700 IronPort-SDR: b7RKvIaagli1NvCXnZL6PrPtf/lS4lqt32VDbwNwTNMw+Ao8X4uSWKPYzOI99CxOplUlxG+m3+ fL9SzeWgsrmA== X-IronPort-AV: E=Sophos;i="5.77,338,1596524400"; d="scan'208";a="340831048" Received: from bricha3-mobl.ger.corp.intel.com ([10.213.193.59]) by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 05 Oct 2020 02:56:41 -0700 Date: Mon, 5 Oct 2020 10:56:37 +0100 From: Bruce Richardson To: Maxime Coquelin Cc: Thomas Monjalon , Stephen Hemminger , dev@dpdk.org, david.marchand@redhat.com, ferruh.yigit@intel.com, jerinj@marvell.com Message-ID: <20201005095637.GA1335@bricha3-MOBL.ger.corp.intel.com> References: <20200907225049.547832-1-thomas@monjalon.net> <20200911155448.2744303-1-thomas@monjalon.net> <20200923224124.494c2e9a@hermes.lan> <9651014.gTjpZimMdh@thomas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] [PATCH v2] kernel: remove igb_uio X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Oct 05, 2020 at 11:11:40AM +0200, Maxime Coquelin wrote: > > > On 10/5/20 10:57 AM, Thomas Monjalon wrote: > > 24/09/2020 07:41, Stephen Hemminger: > >> On Fri, 11 Sep 2020 17:54:48 +0200 > >> Thomas Monjalon wrote: > >> > >>> As decided in the Technical Board in November 2019, > >>> the kernel module igb_uio is moved to the dpdk-kmods repository > >>> in the /linux/igb_uio/ directory. > >>> > >>> Minutes of Technical Board meeting: > >>> https://mails.dpdk.org/archives/dev/2019-November/151763.html > >>> > >>> Signed-off-by: Thomas Monjalon > >>> --- > >>> v2: update few docs (including release notes) > >> > >> Good so far: > >> Acked-by: Stephen Hemminger > >> > >> You may want to address all the references to igb_uio in guides/nics > >> > >> ark.rst > >> axgbe.rst > >> bnx2x.rst > >> bnxt.rst > >> build_and_test.rst > >> ena.rst > >> enic.rst > >> features.rst > >> hns3.rst > >> i40e.rst > >> intel_vf.rst > >> ixgbe.rst > >> liquidio.rst > >> mlx4.rst > >> mlx5.rst > >> nfp.rst > >> qede.rst > >> virtio.rst > > > > igb_uio is still available. > > A next step in deprecation might be to remove igb_uio references. > > > >> What about drivers like ark which don't mention vfio? > > > > They should be updated by their maintainer. > > > >> Does virtio still require igb_uio? or x86 I/O port for doorbell? > >> Or is this just stale language. > > > > Maxime, any update on the use of igb_uio with virtio? > > For sure Virtio don't require igb_uio, I always use vfio myself. > It seems the doc needs an update, I'll try to look at it later in this > release. > Another gap I believe we need to close is that we need some instructions in the GSG for using vfio in noiommu mode, for those running in VMs without an emulated iommu. The VM case is the big one where using regular VFIO may cause problems. I do see in the GSG one mention that it's possible to use VFIO without an IOMMU, but no instructions on how to do so. /Bruce