From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E917AC2D0DB for ; Wed, 22 Jan 2020 09:59:52 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 9837020704 for ; Wed, 22 Jan 2020 09:59:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="lLJV1e16" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9837020704 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=broadcom.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4128F2A62; Wed, 22 Jan 2020 10:59:51 +0100 (CET) Received: from relay.smtp.broadcom.com (relay.smtp.broadcom.com [192.19.211.62]) by dpdk.org (Postfix) with ESMTP id D1A5A2A62 for ; Wed, 22 Jan 2020 10:59:49 +0100 (CET) Received: from dhcp-10-123-153-22.dhcp.broadcom.net (bgccx-dev-host-lnx2.bec.broadcom.net [10.123.153.22]) by relay.smtp.broadcom.com (Postfix) with ESMTP id 7797228D9EE; Wed, 22 Jan 2020 01:59:48 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.10.3 relay.smtp.broadcom.com 7797228D9EE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com; s=dkimrelay; t=1579687188; bh=0LXKvmp/99YEP9hTYKuy9xvdqK5Pf62hgGkx+GUfsaE=; h=From:To:Cc:Subject:Date:From; b=lLJV1e16N6JOYY7r23ADzgOPuqll9pI2ECuXC/SQmz6pw0yUPxeIc2FHFIbLgTcAs eh4skN99snqvfNWhMQPo60CCqUwnoiFXT+DCMiU11Cu4PlkhuJlLOH6Ekqw/yGPiwF b42R8G+4Erzg4kuhJbGSg89Umhju4Ty9z4K8E3pU= From: Kalesh A P To: dev@dpdk.org Cc: thomas@monjalon.net, ferruh.yigit@intel.com, declan.doherty@intel.com Date: Wed, 22 Jan 2020 15:46:51 +0530 Message-Id: <20200122101654.20824-1-kalesh-anakkur.purayil@broadcom.com> X-Mailer: git-send-email 2.10.1 Subject: [dpdk-dev] [RFC PATCH 0/3] librte_ethdev: error recovery support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" From: Kalesh AP This patch adds support for recovery event in rte_eth_event framework. FW error and FW reset conditions would be managed by PMD. Driver uses RTE_ETH_EVENT_INTR_RESET event to notify the applications about the FW reset or error. In such cases, PMD would need recovery events to notify application about PMD has recovered from FW reset or FW error. Kalesh AP (3): librte_ethdev: support device recovery event net/bnxt: notify applications about device reset app/testpmd: handle device recovery event app/test-pmd/testpmd.c | 7 ++++++- drivers/net/bnxt/bnxt_cpr.c | 3 +++ drivers/net/bnxt/bnxt_ethdev.c | 10 ++++++++++ lib/librte_ethdev/rte_ethdev.h | 1 + 4 files changed, 20 insertions(+), 1 deletion(-) -- 2.10.1