[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110426185917.3d033636@nehalam>
Date: Tue, 26 Apr 2011 18:59:17 -0700
From: Stephen Hemminger <shemminger@...tta.com>
To: Rasesh Mody <rmody@...cade.com>
Cc: <netdev@...r.kernel.org>, <davem@...emloft.net>,
<huangj@...cade.com>, <amathur@...cade.com>,
Debashis Dutt <ddutt@...cade.com>
Subject: Re: [RFC PATCH 1/1] bna: Generic Netlink Interface to collect FW
trace
On Tue, 26 Apr 2011 18:51:57 -0700
Rasesh Mody <rmody@...cade.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@...cade.com>
> Signed-off-by: Rasesh Mody <rmody@...cade.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...
--
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists