From: Stephen Hemminger <shemminger@vyatta.com>
To: Rasesh Mody <rmody@brocade.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<huangj@brocade.com>, <amathur@brocade.com>,
Debashis Dutt <ddutt@brocade.com>
Subject: Re: [RFC PATCH 1/1] bna: Generic Netlink Interface to collect FW trace
Date: Tue, 26 Apr 2011 18:59:17 -0700 [thread overview]
Message-ID: <20110426185917.3d033636@nehalam> (raw)
In-Reply-To: <1303869117-780-1-git-send-email-rmody@brocade.com>
On Tue, 26 Apr 2011 18:51:57 -0700
Rasesh Mody <rmody@brocade.com> wrote:
> This is a RFC patch to Brocade BNA 10G Ethernet driver. It adds the generic
> netlink communication interface to the BNA driver to collect firmware traces
> using the in-kernel generic netlink infrastructure. The driver uses the
> "dumpit" handler provided by the generic netlink layer to accomplish this. The
> driver can extend this interface later if required.
>
> As of today, there seems to be no standard mechanism to collect debug
> information such as firmware trace for a given hardware. Generic Netlinki seems
> to provide a suitable option to do the same, without any further
> addition/modification to the existing kernel implementation.
>
> This is a RFC patch inviting suggestions/opinions for improvement/modification
> and requesting consideration for possible inclusion in net-next tree.
>
> Signed-off-by: Debashis Dutt <ddutt@brocade.com>
> Signed-off-by: Rasesh Mody <rmody@brocade.com>
Seems like a lot of work for a debug interface. What about debugfs?
Or is that out of favor now, I can never keep track...
--
next prev parent reply other threads:[~2011-04-27 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 1:51 [RFC PATCH 1/1] bna: Generic Netlink Interface to collect FW trace Rasesh Mody
2011-04-27 1:59 ` Stephen Hemminger [this message]
2011-04-27 2:16 ` Debashis Dutt
2011-04-27 2:17 ` David Miller
2011-04-28 17:51 ` Debashis Dutt
2011-04-28 19:19 ` David Miller
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=20110426185917.3d033636@nehalam \
--to=shemminger@vyatta.com \
--cc=amathur@brocade.com \
--cc=davem@davemloft.net \
--cc=ddutt@brocade.com \
--cc=huangj@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox