lkml.org 
[lkml]   [2019]   [Oct]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH V3 3/3] bnxt_en: Add support to collect crash dump via ethtool
    On Thu, 24 Oct 2019 11:02:41 +0530, Sheetal Tigadoli wrote:
    > From: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
    >
    > Driver supports 2 types of core dumps.
    >
    > 1. Live dump - Firmware dump when system is up and running.
    > 2. Crash dump - Dump which is collected during firmware crash
    > that can be retrieved after recovery.
    > Crash dump is currently supported only on specific 58800 chips
    > which can be retrieved using OP-TEE API only, as firmware cannot
    > access this region directly.
    >
    > User needs to set the dump flag using following command before
    > initiating the dump collection:
    >
    > $ ethtool -W|--set-dump eth0 N
    >
    > Where N is "0" for live dump and "1" for crash dump
    >
    > Command to collect the dump after setting the flag:
    >
    > $ ethtool -w eth0 data Filename
    >
    > v3: Modify set_dump to support even when CONFIG_TEE_BNXT_FW=n.
    > Also change log message to netdev_info().
    >
    > Cc: Jakub Kicinski <jakub.kicinski@netronome.com>
    > Cc: Michael Chan <michael.chan@broadcom.com>
    > Signed-off-by: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
    > Signed-off-by: Sheetal Tigadoli <sheetal.tigadoli@broadcom.com>

    Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>

    \
     
     \ /
      Last update: 2019-10-24 20:57    [W:6.052 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site