From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP; 13 Dec 2015 17:12:43 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,424,1444719600"; d="scan'208";a="859996082" Received: from shilc102.sh.intel.com ([10.239.39.44]) by fmsmga001.fm.intel.com with ESMTP; 13 Dec 2015 17:12:42 -0800 Received: from shecgisg004.sh.intel.com (shecgisg004.sh.intel.com [10.239.29.89]) by shilc102.sh.intel.com with ESMTP id tBE1CdIp028022; Mon, 14 Dec 2015 09:12:39 +0800 Received: from shecgisg004.sh.intel.com (localhost [127.0.0.1]) by shecgisg004.sh.intel.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id tBE1CadR001863; Mon, 14 Dec 2015 09:12:38 +0800 Received: (from hzhan75@localhost) by shecgisg004.sh.intel.com (8.13.6/8.13.6/Submit) id tBE1CZPE001859; Mon, 14 Dec 2015 09:12:35 +0800 From: Helin Zhang To: dev@dpdk.org Date: Mon, 14 Dec 2015 09:12:34 +0800 Message-Id: <1450055554-1828-1-git-send-email-helin.zhang@intel.com> X-Mailer: git-send-email 1.7.4.1 Subject: [dpdk-dev] [PATCH] doc: add knwon issue of PF reset event handling X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2015 01:12:44 -0000 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