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 14C9FA0C45; Wed, 22 Sep 2021 09:34:34 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8ACF44069E; Wed, 22 Sep 2021 09:34:33 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by mails.dpdk.org (Postfix) with ESMTP id AD4A140141 for ; Wed, 22 Sep 2021 09:34:32 +0200 (CEST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 067A4580851; Wed, 22 Sep 2021 03:34:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 22 Sep 2021 03:34:31 -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= Z6UpiBBIgV30dRBpdhQWKFSPureKBQoESgvd6MpWSmI=; b=akIVAvvI+vADEyTm 5G1Z11wicEfWTUco8udLHTvo7pp9+oAWZ+ZU9BVKMTyuvCMfeQj2Ssdm/3D+/GNT ChWiNmsHjjVutJ3oLQ5+bK85k1092nVRKP6hpmdlMeMFpUBYiV0XqcsE1ZQuBtXq N4AvSAg7BN706f1Lg0BuXMqwnv9XOtBjvjSmkoaPPcHqYPJ2ZfeiKi2xOBJgWdQR ECphFX1TbJVUN3Tl90+otPxLx85Qi1dV+6XpDSGCoEHpvfU84N3CtaRbfngd6CLd RWA0G5Yq1WO95Gk5HK4KcRWNjfxAoaJzRT5UUOEU1KBM9VgXVX1Um62WkUMKKl2H 3madjQ== 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=Z6UpiBBIgV30dRBpdhQWKFSPureKBQoESgvd6MpWS mI=; b=ACa76EZBaaFSZKGO9wDY1YyqcZIfzTKCeA8Wytg3rzMWOHcZWxoov9alg hrdvYe4aGuR7SWvFYMbvwBbYgUJygpIAAJBgc5s9PeP7PZW/Jq5qrOn89PoVlkPI CC+enkez6K6Ra6nu74jKdlvigSECMRUOvZLVbZv4XqJD/qdpvI+f8toRz2a5GfE6 hzz5cfboSer7kbfnNz8Ds9t1rkwmWyztUruplpOPHJQmNTl6ky2SkYHgDhJK2AQn 2Bce5waY6tVbaQ2z8WhamXVPS9ttdOglg9x+WLr6TaUVzR7xHv3W7t/dLmvPU9Cu g1Ud4HpjxAr1CiuGpTp/uTVR5TyBA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudeiiedgudduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdej ueeiiedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Sep 2021 03:34:27 -0400 (EDT) From: Thomas Monjalon To: Jerin Jacob Cc: Jerin Jacob , dpdk-dev , David Marchand , "Richardson, Bruce" , Dmitry Kozlyuk , Narcisa Ana Maria Vasile , "Dmitry Malloy (MESHCHANINOV)" , Pallavi Kadam , "Ananyev, Konstantin" , "Ruifeng Wang (Arm Technology China)" , David Christensen , Stephen Hemminger , Olivier Matz , Ferruh Yigit , Andrew Rybchenko , Ajit Khaparde , Morten =?ISO-8859-1?Q?Br=F8rup?= Date: Wed, 22 Sep 2021 09:34:25 +0200 Message-ID: <6691908.cbmxaGqiiQ@thomas> In-Reply-To: References: <20210817032723.3997054-1-jerinj@marvell.com> <7007516.EuRbNVrdOy@thomas> 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" 21/09/2021 19:54, Jerin Jacob: > On Tue, Sep 21, 2021 at 11:00 PM Thomas Monjalon wrote: > > > > 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 abstracts the execution environment/architecture(See Arch Info in > log)[1] details to capture > details on fault handlers to enable additional details on fault from > DPDK application for > additional debugging information. Just like Kernel prints its OOPS on fault. Not sure it is a good direction to achieve the same features as a kernel. In recent years, the idea was to make DPDK a focused library. > > It looks something to be handled freely by the application > > without DPDK forcing anything. > > This NOT enforcing application to use DPDK OOPS handler, instead, if > registered then > it uses the default handler. > > Even if the default handler is registered it invokes the application > handler if the application registers > the fault handler. So there is not difference in behavior. OK > > What is the benefit for other DPDK features? > > Could you clarify this question a bit more? I mean is it used by other parts of DPDK, or just a standalone feature? > > Which problem is it solving? > > Better debug trace on fault for DPDK application. Instead of faulting > with no information. It does not look to be in the scope of DPDK, or I miss something.