From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next 0/5] add v2 FW logging for ice driver
Date: Wed, 30 Nov 2022 16:39:23 -0800 [thread overview]
Message-ID: <6714c391-1d52-dfdd-1a89-311912494796@intel.com> (raw)
In-Reply-To: <20221128214749.110-1-paul.m.stillwell.jr@intel.com>
On 11/28/2022 1:47 PM, Paul M Stillwell Jr wrote:
> FW log support was added to the ice driver, but that version is no
> longer supported. There is a newer version of FW logging (v2) that
> adds more controls knobs to get the exact data out of the FW
> for debugging.
>
> Additionally, instead of dumping the FW log output to syslog,
> dump it to debugfs. The FW log data is really just binary
> data that the FW log team decodes to determine what happens so the
> translation from binary to some text output just slows things down
> and results in potential dropped data. The structure for the debugfs
> entry is: /sys/kernel/debug/ice/<pci device>/fwlog
>
> Once enabled the FW log data is received as ARQ events that the driver
> processes.
>
> The FW logging is across all the PFs on the device, so restrict the
> commands to only PF0.
>
> The following new device parameters are added:
> - fwlog_supported (read-only): does the FW support FW logging
> - fwlog_enabled (read/write): is FW logging currently running
> - fwlog_level (read/write): the log level enabled, valid values are
> Each level includes the messages from the previous/lower level
> 0 - no logging
> 1 - error logging
> 2 - warning logging
> 3 - normal logging
> 4 - verbose logging
> - fwlog_resolution (read/write): the number of log messages to included
> in a single ARQ event. The range is 1-128 (1 means push every log
> message, 128 means push only when the max AQ command buffer is full).
> The suggested value is 10.
>
> This patch series adds the following set of devlink commands:
>
> devlink dev param set <pci dev> name fwlog_enabled value <true/false> cmode runtime
> devlink dev param set <pci dev> name fwlog_level value <0-4> cmode runtime
> devlink dev param set <pci dev> name fwlog_resolution value <1-128> cmode runtime
>
> Paul M Stillwell Jr (5):
> ice: remove FW logging code
> ice: enable devlink to check FW logging status
> ice: add ability to query/set FW log level and resolution
> ice: disable FW logging on driver unload
> ice: use debugfs to output FW log data
>
> drivers/net/ethernet/intel/ice/Makefile | 4 +-
> drivers/net/ethernet/intel/ice/ice.h | 24 ++
> .../net/ethernet/intel/ice/ice_adminq_cmd.h | 164 ++++----
> drivers/net/ethernet/intel/ice/ice_common.c | 218 +---------
> drivers/net/ethernet/intel/ice/ice_debugfs.c | 109 +++++
> drivers/net/ethernet/intel/ice/ice_devlink.c | 205 ++++++++-
> drivers/net/ethernet/intel/ice/ice_fwlog.c | 394 ++++++++++++++++++
> drivers/net/ethernet/intel/ice/ice_fwlog.h | 56 +++
> drivers/net/ethernet/intel/ice/ice_main.c | 99 ++++-
> drivers/net/ethernet/intel/ice/ice_type.h | 23 +-
Please add Documentation for this
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-12-01 0:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 21:47 [Intel-wired-lan] [PATCH net-next 0/5] add v2 FW logging for ice driver Paul M Stillwell Jr
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 1/5] ice: remove FW logging code Paul M Stillwell Jr
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 2/5] ice: enable devlink to check FW logging status Paul M Stillwell Jr
2022-12-01 0:39 ` Tony Nguyen
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 3/5] ice: add ability to query/set FW log level and resolution Paul M Stillwell Jr
2022-11-29 11:48 ` Wilczynski, Michal
2022-11-29 13:30 ` Alexander Lobakin
2022-11-29 21:31 ` Paul M Stillwell Jr
2022-12-01 0:39 ` Tony Nguyen
2022-12-09 0:00 ` Paul M Stillwell Jr
2022-12-01 7:36 ` Paul Menzel
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 4/5] ice: disable FW logging on driver unload Paul M Stillwell Jr
2022-11-29 12:05 ` Wilczynski, Michal
2022-11-29 21:31 ` Paul M Stillwell Jr
2022-12-01 0:40 ` Tony Nguyen
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 5/5] ice: use debugfs to output FW log data Paul M Stillwell Jr
2022-11-29 13:53 ` Paul Menzel
2022-11-29 21:28 ` Paul M Stillwell Jr
2022-12-01 0:40 ` Tony Nguyen
2022-12-09 18:32 ` Paul M Stillwell Jr
2022-12-01 0:39 ` Tony Nguyen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 23:27 [Intel-wired-lan] [PATCH net-next 0/5] add v2 FW logging for ice driver Paul M Stillwell Jr
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=6714c391-1d52-dfdd-1a89-311912494796@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=paul.m.stillwell.jr@intel.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