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 1CDD3A0C45; Tue, 21 Sep 2021 19:54:42 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9B59040151; Tue, 21 Sep 2021 19:54:41 +0200 (CEST) Received: from mail-il1-f177.google.com (mail-il1-f177.google.com [209.85.166.177]) by mails.dpdk.org (Postfix) with ESMTP id D3E2D4003C for ; Tue, 21 Sep 2021 19:54:40 +0200 (CEST) Received: by mail-il1-f177.google.com with SMTP id b15so23696459ils.10 for ; Tue, 21 Sep 2021 10:54:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Om1A9pgkdPSHiaeLonF3hiIeLTUvjjUh8Noqcyzr63Q=; b=C2YX0OEbp5bs7hehms4wVcqoBEvXfw1mqkUDGENHGmMufRPJ3NvTVWpO5l9cNaCRCX 6XOBiYeCU9+98ukPaia21Mk/8Zgl4GM+tdnedzBbYOowCD/BJExF/IgCiBOQO+5FVwSH zpfZhVe/LlfAL/u909XsxQMDMdS30FBv++FAPrG+6WE+VA4M71lS/p1LWTDUBZ4imco9 RUR0Dp3RRZbpRIJG9RqJNICwldQYn82+17F4tsn7CG6g8eFDY23mQ6eafU18aBpA4fdr 515QuFb5YfVY5LusrRrJAtny4bkP5KmCDur/bg1Tsouxa5IDSXJwa80aSZ9NV0YhCpTC dOYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Om1A9pgkdPSHiaeLonF3hiIeLTUvjjUh8Noqcyzr63Q=; b=SmAIgrTZnHC02zhxZDMoRd7Y6rHm9ZYrgvv1eCtpJOPSTPV1ipkIkhB0xSEljaVw24 xSlvYwdEvvAdnK/SL6oAT2V3YXAaKOUzYiZijRhzXwAyC+nAeMeG5Ryx0rJxRkHBboit NwtIU3O4IU3U95EyCaRsJNZhih1SRZDlGfxm2fiCnaLQcFYLGrYHNI2Zp1e9cdXgoQb7 FlMZhN+UeLntYdvckG9rBjyDUj5mhCPABS/BiBhf/npMt3WsIEW6amN2EhKsMISXooC/ YQ+lCjttumD+rveOMkt895yWSFwUBTJFZYYrRt0ZGYX3tvIPMPHj+ASYBpdzX1WL+HrL l2iA== X-Gm-Message-State: AOAM533dbGZQpl9IDRkL/YbtD0N6dtExoNH8/drwdoKf99nxTuuIHhEf ZBVXwLmc9lm42BtHC2XPDvz/u9Z+QVu1olgugZs= X-Google-Smtp-Source: ABdhPJwujy3VYeWIoXeC4Ot9D4PE/PDeO4B0V2/8mrCIj/yKfWn+CNSVBHRpdkgzHduLG9p3zRbJKQGip8fC9PUlPMw= X-Received: by 2002:a92:c548:: with SMTP id a8mr15164804ilj.295.1632246880113; Tue, 21 Sep 2021 10:54:40 -0700 (PDT) MIME-Version: 1.0 References: <20210817032723.3997054-1-jerinj@marvell.com> <20210906041732.1019743-1-jerinj@marvell.com> <7007516.EuRbNVrdOy@thomas> In-Reply-To: <7007516.EuRbNVrdOy@thomas> From: Jerin Jacob Date: Tue, 21 Sep 2021 23:24:13 +0530 Message-ID: To: Thomas Monjalon 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 , =?UTF-8?Q?Morten_Br=C3=B8rup?= Content-Type: text/plain; charset="UTF-8" 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" 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. > 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. > What is the benefit for other DPDK features? Could you clarify this question a bit more? > Which problem is it solving? Better debug trace on fault for DPDK application. Instead of faulting with no information. [1] Backtrace: ---------- [ 0x55e8b56d5cee]: test_oops_generate()+0x75 [ 0x55e8b5459843]: unit_test_suite_runner()+0x1aa [ 0x55e8b56d605c]: test_oops()+0x13 [ 0x55e8b544bdfc]: cmd_autotest_parsed()+0x55 [ 0x55e8b6063a0d]: cmdline_parse()+0x319 [ 0x55e8b6061dea]: cmdline_valid_buffer()+0x35 [ 0x55e8b6066bd8]: rdline_char_in()+0xc48 [ 0x55e8b606221c]: cmdline_in()+0x62 [ 0x55e8b6062495]: cmdline_interact()+0x56 [ 0x55e8b5459314]: main()+0x65e [ 0x7f54b25d2b25]: __libc_start_main()+0xd5 [ 0x55e8b544bc9e]: _start()+0x2e Arch info: ---------- R8 : 0x0000000000000000 R9 : 0x0000000000000000 R10: 0x00007f54b25b8b48 R11: 0x00007f54b25e7930 R12: 0x00007fffc695e610 R13: 0x0000000000000000 R14: 0x0000000000000000 R15: 0x0000000000000000 RAX: 0x0000000000000005 RBX: 0x0000000000000001 RCX: 0x00007f54b278a943 RDX: 0x3769043bf13a2594 RBP: 0x00007fffc6958340 RSP: 0x00007fffc6958330 RSI: 0x0000000000000000 RDI: 0x000055e8c4c1e380 RIP: 0x000055e8b56d5cee EFL: 0x0000000000010246 Stack dump: ---------- 0x7fffc6958330: 0x6000000 0x7fffc6958334: 0x0 0x7fffc6958338: 0x30cfeac5 0x7fffc695833c: 0x0 0x7fffc6958340: 0xe08395c6 0x7fffc6958344: 0xff7f0000 0x7fffc6958348: 0x439845b5 0x7fffc695834c: 0xe8550000 0x7fffc6958350: 0x0 0x7fffc6958354: 0xb000000 0x7fffc6958358: 0x20445bb9 0x7fffc695835c: 0xe8550000 0x7fffc6958360: 0x925506b6 0x7fffc6958364: 0x0 0x7fffc6958368: 0x0 0x7fffc695836c: 0x0 Code dump: ---------- 0x55e8b56d5cee: 0xc7000000 0x55e8b56d5cf2: 0xeb12 0x55e8b56d5cf6: 0xfb6054b 0x55e8b56d5cfa: 0x87540f84 0x55e8b56d5cfe: 0xc07407b8 0x55e8b56d5d02: 0x0 0x55e8b56d5d06: 0xeb05b8ff 0x55e8b56d5d0a: 0xffffffc9 0x55e8b56d5d0e: 0xc3554889 0x55e8b56d5d12: 0xe54881ec 0x55e8b56d5d16: 0xc0000000 0x55e8b56d5d1a: 0x89bd4cff 0x55e8b56d5d1e: 0xffff4889 0x55e8b56d5d22: 0xb540ffff >