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 BC24CA04A4; Wed, 2 Mar 2022 18:25:09 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DB9ED42783; Wed, 2 Mar 2022 18:24:26 +0100 (CET) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id 7B60442756; Wed, 2 Mar 2022 18:24:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646241863; x=1677777863; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=V7P18K/pcc20AuC3DAfsJsA5uJRnQmkY5JMuQHfUfik=; b=J0b8nvX8r/hifVspRa9ryqiEde3vdxGSUT8j7C/vsyvxABgCzT5DLyJp QbjYDkbus/aPw+N+aanbwo0wIk2BuIQfzxlwTwVfvqsjmI1qnGYaY2pli D4uTac+nSbZysCFcGb4ksvZE4WK714xW9MCYUOZQKXlsBPhT3TyfZWEQB CzC/PbUDcSjJ2f7DDyTy1RdYx52XMJRth8lxMHtf5O+4B4M/4sB3doiJL iDwDGcR/OXXBE1kd/owKLwDOQ3Av7n/Yn8qPqxCU5rA7Inl3P8P5h7Sfp GXVTb9Jx/B8K5sroMldKNXSkfwEaoVJsMR8GhXHkATBuWTa8FuYwX85yN g==; X-IronPort-AV: E=McAfee;i="6200,9189,10274"; a="314177974" X-IronPort-AV: E=Sophos;i="5.90,149,1643702400"; d="scan'208";a="314177974" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Mar 2022 09:24:20 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,149,1643702400"; d="scan'208";a="551348182" Received: from silpixa00399126.ir.intel.com ([10.237.223.34]) by orsmga008.jf.intel.com with ESMTP; 02 Mar 2022 09:24:19 -0800 From: Bruce Richardson To: dev@dpdk.org Cc: stable@dpdk.org, Bruce Richardson Subject: [PATCH 9/9] doc/linux_gsg: change informational warnings to notes Date: Wed, 2 Mar 2022 17:22:17 +0000 Message-Id: <20220302172217.472279-10-bruce.richardson@intel.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220302172217.472279-1-bruce.richardson@intel.com> References: <20220302172217.472279-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. 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 ef91999dd9..03cf264a0a 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