From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id DBE2AA0032; Wed, 16 Mar 2022 14:47:07 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ABE43411C9; Wed, 16 Mar 2022 14:46:24 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mails.dpdk.org (Postfix) with ESMTP id 93E0541158; Wed, 16 Mar 2022 14:46:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1647438374; x=1678974374; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=i7sAb+4CXMVETEqtFbHMACw20Dz9ht57/zvVKBxNcAE=; b=GKwItvKIZHUaEhizxByk1LnvQVvL+B3RZNkN1445B7JQ1wQZyQpjVwXm 8n7NVa6rC94a8iMCoLU9O+Jnq9+DSeGJ3SbK1ShWanBzYl5XKkUThbC4F Gk75tB3VT1heI/bSb+byxDBLelL3N+iLmG7pfMsgA8FjlSsxdMlVHtQ+b e50yoEf5DZgawQZ3fKVs6n+plMAKbjKSUJ66v6If6nlypyFWvEkAtCv20 Xr76f4q3viDoEor5tvAIvQ7oTKVJO4upM1viSzBxUwfSP/D0MPU+/bWmA +fS4uYObZXmxvfrX4y1IKsq+DVMCHyUEo7fdTogTqdBbgEUrUauSDLkrC g==; X-IronPort-AV: E=McAfee;i="6200,9189,10286"; a="256780600" X-IronPort-AV: E=Sophos;i="5.90,186,1643702400"; d="scan'208";a="256780600" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Mar 2022 06:46:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,186,1643702400"; d="scan'208";a="714606538" Received: from silpixa00399126.ir.intel.com ([10.237.223.34]) by orsmga005.jf.intel.com with ESMTP; 16 Mar 2022 06:46:11 -0700 From: Bruce Richardson To: dev@dpdk.org Cc: Bruce Richardson , stable@dpdk.org Subject: [PATCH v2 9/9] doc: change informational warnings to notes in Linux GSG Date: Wed, 16 Mar 2022 13:45:51 +0000 Message-Id: <20220316134551.1099599-10-bruce.richardson@intel.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220316134551.1099599-1-bruce.richardson@intel.com> References: <20220302172217.472279-1-bruce.richardson@intel.com> <20220316134551.1099599-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org There are two warnings in the VFIO section about limitations of VFIO and limitations on who can bind/unbind devices. Since these don't actually describe any unsafe conditions, and are more informational, we can change these to notes. This also helps emphasise the other warnings in the documents which flag genuine security concerns. Cc: stable@dpdk.org Signed-off-by: Bruce Richardson --- doc/guides/linux_gsg/linux_drivers.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/linux_gsg/linux_drivers.rst b/doc/guides/linux_gsg/linux_drivers.rst index 8320db44d9..2e4c80ebd3 100644 --- a/doc/guides/linux_gsg/linux_drivers.rst +++ b/doc/guides/linux_gsg/linux_drivers.rst @@ -48,7 +48,7 @@ by calling the script with the ``--help`` or ``--usage`` options. Note that the UIO or VFIO kernel modules to be used, should be loaded into the kernel before running the ``dpdk-devbind.py`` script. -.. warning:: +.. note:: Due to the way VFIO works, there are certain limitations to which devices can be used with VFIO. @@ -62,7 +62,7 @@ should be loaded into the kernel before running the ``dpdk-devbind.py`` script. Therefore, the bridge driver should also be unbound from the bridge PCI device for VFIO to work with devices behind the bridge. -.. warning:: +.. note:: While any user can run the ``dpdk-devbind.py`` script to view the status of the network ports, -- 2.32.0