netdev - Re: [PATCH net-next v3 0/4] sfc: add MCDI tracing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20150525.001138.1265925235771537042.davem@davemloft.net>
Date:	Mon, 25 May 2015 00:11:38 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ecree@...arflare.com
Cc:	netdev@...r.kernel.org, linux-net-drivers@...arflare.com
Subject: Re: [PATCH net-next v3 0/4] sfc: add MCDI tracing

From: Edward Cree <ecree@...arflare.com>
Date: Fri, 22 May 2015 20:19:25 +0100

> This patchset adds support for logging MCDI (Management-Controller-to-
>  Driver Interface) interactions between the sfc driver and a bound device,
>  to aid in debugging.
> Solarflare has a tool to decode the resulting traces and will look to
>  open-source this if there is any external interest, but the protocol is
>  already detailed in drivers/net/ethernet/sfc/mcdi_pcol.h.
> The logging buffer we allocate per MCDI context is a work area for
>  constructing each individual message before logging it with netif_info.
> The reason the buffer is long-lived is simply to avoid the overhead of
>  allocating and freeing it every MCDI call, since MCDIs are already known
>  to be serialised for other reasons.
> 
> --
> v3: add some explanations to cover letter and patch #4
> v2: avoid long lines in cover letter; fix multiline comment style

Patch #4 doesn't apply cleanly to net-next, please respin.

Thank you.
--
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