From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
davem@davemloft.net, ganeshgr@chelsio.com, nirranjan@chelsio.com,
indranil@chelsio.com, rahul.lakkireddy@chelsio.com
Subject: Appending firmware/hardware dump to vmcore during kernel panic
Date: Tue, 20 Feb 2018 16:26:14 +0530 [thread overview]
Message-ID: <20180220105613.GA9766@chelsio.com> (raw)
Hi all,
We have a requirement to collect firmware/hardware state of the
underlying NIC during kernel panic. We are doing this in cxgb4
driver, using panic notifier list [1]. cxgb4 registers a callback
function to the panic notifier list, which gets invoked during kernel
panic. In the callback function, firmware/hardware dump is collected
into pre-allocated buffer and then extracted later from the vmcore,
for post-analysis.
Is this approach of using panic notifier correct? Any suggestions are
much appreciated.
Thanks,
Rahul
[1] https://patchwork.ozlabs.org/patch/873830/
reply other threads:[~2018-02-20 10:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180220105613.GA9766@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=indranil@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.