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 42DD6427E4 for ; Mon, 20 Mar 2023 17:06:16 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3A1D442B71; Mon, 20 Mar 2023 17:06:16 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 6AA57406BC; Mon, 20 Mar 2023 17:06:13 +0100 (CET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 1BF865C0058; Mon, 20 Mar 2023 12:06:13 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 20 Mar 2023 12:06:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1679328373; x=1679414773; bh=+aZsN2NLUDcSbWQqK9wC9zXKhb6/bzBfzkR yPxAaUFQ=; b=lq7JUHUdr4xvS6m3ifZoRk2j0jRoxmMmskJeCljh8K5N56c2flr oENbDF2H+ZLHjFnhkROlyo//CAStUg1rMG9/3LWUeE0DIwhbVdtEh6YfbZZHjyUb f3HFBnsWxeYsoxAqZATl3ohWYszyKozPKLya8hkNQjJNWEyqzF9j3esg61AIYTxO dMxh5Gt4v54syAro8HK38q04Obz2yIizO9hHJlB1u6s2siF+tJ2akXFUTI2a3ybj rN7aPZ7MDQyZ9bX9edw9RMw4T8oaZIrQg14Gvf+45TUkG3nrDEm0swT0hPjfOPTC 4L4kYfgx5necNc4sckfuPOj6+JyxEj9Vqpw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1679328373; x=1679414773; bh=+aZsN2NLUDcSbWQqK9wC9zXKhb6/bzBfzkR yPxAaUFQ=; b=F3guJxl7v3/ItSxwv9zPfz50doaqIrzicJWLKsIVi74DWJOHpQI 1E5T1o2/MP6n92A6+jsoUitYp4OxVULGU+u63LkXpScqAErmyWLtB39H7WvsGdpJ TrAi/AIicj9UAVG2+8trbOO1qFyfz/vdrrxCXWMuZoK5W5daFJoDEZA8XWyCymB1 rFRt5plRI+LW34X7T0l0fMqsPcXNAiAwJ6w6ce/v5hB3MYIHFfivYXQTJsLya0N5 PLr+lVq7WPf25TpILd8Af3QJaL2+bgV35TS+oD98ogCPDbvK4xEhidUUf6aXZP8K QcPwwqWMDhxuDGpfQxFFG3/XiqYFSHw3v/Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdefkedgkeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 20 Mar 2023 12:06:11 -0400 (EDT) From: Thomas Monjalon To: Wei Huang Cc: dev@dpdk.org, david.marchand@redhat.com, stable@dpdk.org, rosen.xu@intel.com, tianfei.zhang@intel.com, qi.z.zhang@intel.com Subject: Re: [PATCH v1] raw/ifpga: remove virtual device unplug operation Date: Mon, 20 Mar 2023 17:06:10 +0100 Message-ID: <6411222.K2JlShyGXD@thomas> In-Reply-To: <20230316204445.360330-1-wei.huang@intel.com> References: <20230316204445.360330-1-wei.huang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org 16/03/2023 21:44, Wei Huang: > VDEV bus has implemented cleanup() function to perform cleanup for > devices on the bus during eal_cleanup(), so there is no need for > ifpga driver to record virtual devices and unplug them. Why no need? If the application wants to explicitly remove a device, what happens?