From mboxrd@z Thu Jan 1 00:00:00 1970 From: Helin Zhang Subject: [PATCH] doc: add knwon issue of PF reset event handling Date: Mon, 14 Dec 2015 09:12:34 +0800 Message-ID: <1450055554-1828-1-git-send-email-helin.zhang@intel.com> To: dev@dpdk.org Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 89DCF567E for ; Mon, 14 Dec 2015 02:12:43 +0100 (CET) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Add a known issue to warn that PF reset event/request is not handled by any VF drivers till 2.2, and which should be fixed in the future. Signed-off-by: Helin Zhang --- doc/guides/rel_notes/release_2_2.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst index a0035b7..a99b6c4 100644 --- a/doc/guides/rel_notes/release_2_2.rst +++ b/doc/guides/rel_notes/release_2_2.rst @@ -273,6 +273,11 @@ Known Issues As the l3fwd example application requires this info, the i40e vector driver must be disabled to benefit of the packet type with i40e. +* Some (possibly all) VF drivers (e.g. i40evf) do not handle any PF reset + events/requests in VF driver, that means VF driver may not work after a + PF reset in host side. The workaround is to avoid triggering any PF reset + events/requests on host side, or wait future fixes. + API Changes ----------- -- 1.9.3