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 ED46FA0C45; Tue, 21 Sep 2021 19:30:51 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8576D40151; Tue, 21 Sep 2021 19:30:51 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by mails.dpdk.org (Postfix) with ESMTP id DEB914003C for ; Tue, 21 Sep 2021 19:30:50 +0200 (CEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 6DE6B580B8D; Tue, 21 Sep 2021 13:30:48 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 21 Sep 2021 13:30:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= ZgoM5mAn0guivMqMQsUw+iVFvDAcxkGpo5jcl9NufOM=; b=JcepA9tR31KdV205 XeMXoHQten9HXWauFiucquLtCbimSPcd0NMZHosCix5w3oMvRqC/3SzRQ+EdrKLH NWJsYCZjO1PK+OtblNZocamfsNMGXwH+RydX6Coavf4pBFZU1m/bgpv8AD2bZZoW 5hvEwSIkGdcvGoFhZyDjAQrDunicRO36rm1eVrThZQeOsvH/uCc6crDmvL3FAiBq ShOYAuLSHUsqwXlEcSAs7lkMfpWPyRnlmsmtxUojmSLb+9qetYJiRLN+24M7KvuQ Hhc4dOQbpONAXMD3h+gp7oOE76D78ysczuSto1unjZXpcwfXOqDigxzNFN5Th51M MLnC8A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=ZgoM5mAn0guivMqMQsUw+iVFvDAcxkGpo5jcl9Nuf OM=; b=PcmKGSSTVm6tLPqcqUSNdW7zWSUpFl9oH8Z+JK2m0HdZLGD9+coOwcd1g H2+4pSPWj+Hby8WtV5cvFWhtIu0RekhVg+78ev9P6lvLN1zOFqzo59GOBvdMhzI3 DMJ6Xd/l6tJ8rsArY5da2mZ3c/Y4MpfvnOYZQGQ8auD/lWwBLIsU+AxLn5J6BIv3 n/E7bHNIPoGnu1VSSKKoa+R6DVBYasJq9EsPSxlEECigOacspOBHnQS2ScjkrktB xUmU6pm8cvIXOvI1bSycqgHEVSB/nDob1x1df16Mw8nc7gxnPlHEHVZQNdOixPFd klCAURnt663vZkIBkzAAtRrXcjG7A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudeigedguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdej ueeiiedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 21 Sep 2021 13:30:43 -0400 (EDT) From: Thomas Monjalon To: Jerin Jacob Cc: dev@dpdk.org, david.marchand@redhat.com, bruce.richardson@intel.com, dmitry.kozliuk@gmail.com, navasile@linux.microsoft.com, dmitrym@microsoft.com, pallavi.kadam@intel.com, konstantin.ananyev@intel.com, ruifeng.wang@arm.com, drc@linux.vnet.ibm.com, stephen@networkplumber.org, olivier.matz@6wind.com, ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru, ajit.khaparde@broadcom.com, mb@smartsharesystems.com Date: Tue, 21 Sep 2021 19:30:41 +0200 Message-ID: <7007516.EuRbNVrdOy@thomas> In-Reply-To: <20210906041732.1019743-1-jerinj@marvell.com> References: <20210817032723.3997054-1-jerinj@marvell.com> <20210906041732.1019743-1-jerinj@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/6] support oops handling X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" 06/09/2021 06:17, jerinj@marvell.com: > It is handy to get detailed OOPS information like Linux kernel > when DPDK application crashes without losing any of the features > provided by coredump infrastructure by the OS. > > This patch series introduces the APIs to handle OOPS in DPDK. I don't understand how it is related to DPDK. It looks something to be handled freely by the application without DPDK forcing anything. What is the benefit for other DPDK features? Which problem is it solving?