Message ID | 20240701223424.427588-1-nicolas.chautru@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 16E1745540; Tue, 2 Jul 2024 00:34:14 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F1834402B9; Tue, 2 Jul 2024 00:34:13 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.16]) by mails.dpdk.org (Postfix) with ESMTP id 0737C40289 for <dev@dpdk.org>; Tue, 2 Jul 2024 00:34:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1719873253; x=1751409253; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=zT6zPu+ArGf0skRqiptViCUx3IkHTGplQYz/JWvSGX0=; b=d421SxteyKwT6RSGPcWPzZSuLicTMMw686TxkMaAZ7vKn4gtpluOY/74 o5g1iwWzGYVft3DQ8OQYEMFWMIIjBfVUySXyqDFkPt0gyYz/u6H/Nu7gN /p6HGeYrsfRzNJQIhq1e9bidlaJ4ybPtmyCoUXbzoPPLnZ9qrZ+YnPT5Q B7+UFKDFH12dE/u7AHmIvPrsUBLCQO7Jb719z3bbqrpDK6QjatW2DdK6F 1kCoCOtyFG6HtPSIQeBL7mzn8W2v0se6sC6i5eIkyqwRxnkBXB+PTfKE+ wvKXNlrVL316l8oKQ/x9yRC5qmqPrn1WN81r9SL8Nox3zVUJXM17M3Wvt w==; X-CSE-ConnectionGUID: Q0tfdUn1RmqNlKmcwtr17w== X-CSE-MsgGUID: Cfn/qbPsTpShKfU4XUnSKw== X-IronPort-AV: E=McAfee;i="6700,10204,11120"; a="12345767" X-IronPort-AV: E=Sophos;i="6.09,177,1716274800"; d="scan'208";a="12345767" Received: from orviesa010.jf.intel.com ([10.64.159.150]) by fmvoesa110.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Jul 2024 15:34:12 -0700 X-CSE-ConnectionGUID: RnqTSVdPTxGuP4IbT1xjAw== X-CSE-MsgGUID: ln5xLTUwTp+EWBbc11vCeg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.09,177,1716274800"; d="scan'208";a="45573288" Received: from spr-npg-bds1-eec2.sn.intel.com (HELO spr-npg-bds1-eec2..) ([10.233.181.123]) by orviesa010.jf.intel.com with ESMTP; 01 Jul 2024 15:34:11 -0700 From: Nicolas Chautru <nicolas.chautru@intel.com> To: dev@dpdk.org, maxime.coquelin@redhat.com Cc: hemant.agrawal@nxp.com, david.marchand@redhat.com, hernan.vargas@intel.com, Nicolas Chautru <nicolas.chautru@intel.com> Subject: [PATCH v1 0/2] bbdev: dump debug information Date: Mon, 1 Jul 2024 15:34:22 -0700 Message-Id: <20240701223424.427588-1-nicolas.chautru@intel.com> X-Mailer: git-send-email 2.34.1 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org |
Series |
bbdev: dump debug information
|
|
Message
Chautru, Nicolas
July 1, 2024, 10:34 p.m. UTC
Hi Maxime. Adding new support to support troubleshooting. This provides to the application an API to dump into file information to help troubleshoot issue on a queue. Some of it is tracked at bbdev level and some extra information can be tracked as an option at PMD level. This is for 24.11. In practive logging is not enabled at run time, but information can be dump into file when an issue happens and requires extra information. This collates now multiple source of errors detected notably at driver level made more explicit. Thanks, Nic Nicolas Chautru (2): bbdev: add new function to dump debug information baseband/acc: improvement to logging mechanism drivers/baseband/acc/acc_common.h | 37 +++++ drivers/baseband/acc/rte_vrb_pmd.c | 128 +++++++++++++---- lib/bbdev/rte_bbdev.c | 214 +++++++++++++++++++++++++++++ lib/bbdev/rte_bbdev.h | 41 ++++++ lib/bbdev/rte_bbdev_pmd.h | 9 ++ lib/bbdev/version.map | 4 + 6 files changed, 406 insertions(+), 27 deletions(-)