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 v9 5/5] ice: add ability to enable FW logging and capture data
Date: Fri, 3 Mar 2023 15:23:31 -0800 [thread overview]
Message-ID: <5aaa7525-cfee-225f-940c-78d646484c6d@intel.com> (raw)
In-Reply-To: <20230302215109.124-6-paul.m.stillwell.jr@intel.com>
On 3/2/2023 1:51 PM, Paul M Stillwell Jr wrote:
> Once the FW logging is configured then users need to be able to enable
> logging and capture the data. To enable/disable FW logging use 'enable
> fwlog' and 'disable fwlog'. An example command to enable FW logging:
>
> echo enable fwlog > /sys/kernel/debug/ice/0000\:18\:00.0/fwlog
>
> Once logging is enable the user should read the data using something
> like:
>
> cat /sys/kernel/debug/ice/0000\:18\:00.0/fwlog > log_data.bin
There should be documentation for this feature;
Documentation/networking/device_drivers/ethernet/intel/ice.rst?
> The output file is a binary file that will be decoded by the FW
> team for debugging.
Perhaps 'by Intel' instead of 'by the FW team'
>
> Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
> ---
[...]
> index a611e0d98bd0..68ab19678dbe 100644
> --- a/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h
> +++ b/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h
> @@ -2075,7 +2075,9 @@ enum ice_aqc_fw_logging_mod {
> };
>
> /* Set FW Logging configuration (indirect 0xFF30)
> + * Register for FW Logging (indirect 0xFF31)
This should go with the patch that added the
'ice_aqc_opc_fw_logs_register = 0xFF31,'
entry...
Also, the defines related to the command should be brought in with the
command instead of all at the beginning.
(These:
+#define ICE_AQC_FW_LOG_CONF_UART_EN BIT(0)
+#define ICE_AQC_FW_LOG_CONF_AQ_EN BIT(1)
+#define ICE_AQC_FW_LOG_QUERY_REGISTERED BIT(2)
+#define ICE_AQC_FW_LOG_CONF_SET_VALID BIT(3)
+#define ICE_AQC_FW_LOG_AQ_REGISTER BIT(0)
+#define ICE_AQC_FW_LOG_AQ_QUERY BIT(2)
+#define ICE_AQC_FW_LOG_PERSISTENT BIT(0)
)
> * Query FW Logging (indirect 0xFF32)
> + * FW Log Event (indirect 0xFF33)
> */
> struct ice_aqc_fw_log {
> u8 cmd_flags;
> @@ -2375,6 +2377,7 @@ enum ice_adminq_opc {
> ice_aqc_opc_fw_logs_config = 0xFF30,
> ice_aqc_opc_fw_logs_register = 0xFF31,
> ice_aqc_opc_fw_logs_query = 0xFF32,
> + ice_aqc_opc_fw_logs_event = 0xFF33,
> };
>
_______________________________________________
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:[~2023-03-03 23:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 21:51 [Intel-wired-lan] [PATCH net-next v9 0/5] add v2 FW logging for ice driver Paul M Stillwell Jr
2023-03-02 21:51 ` [Intel-wired-lan] [PATCH net-next v9 1/5] ice: remove FW logging code Paul M Stillwell Jr
2023-03-02 21:51 ` [Intel-wired-lan] [PATCH net-next v9 2/5] ice: enable debugfs to check FW logging status Paul M Stillwell Jr
2023-03-03 23:21 ` Tony Nguyen
2023-03-06 22:00 ` Paul M Stillwell Jr
2023-03-02 21:51 ` [Intel-wired-lan] [PATCH net-next v9 3/5] ice: add ability to set FW log configuration Paul M Stillwell Jr
2023-03-03 1:23 ` kernel test robot
2023-03-03 23:21 ` Tony Nguyen
2023-03-06 22:11 ` Paul M Stillwell Jr
2023-03-02 21:51 ` [Intel-wired-lan] [PATCH net-next v9 4/5] ice: enable FW logging based on stored configuration Paul M Stillwell Jr
2023-03-03 23:22 ` Tony Nguyen
2023-03-06 22:14 ` Paul M Stillwell Jr
2023-03-02 21:51 ` [Intel-wired-lan] [PATCH net-next v9 5/5] ice: add ability to enable FW logging and capture data Paul M Stillwell Jr
2023-03-03 23:23 ` Tony Nguyen [this message]
2023-03-08 23:22 ` 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=5aaa7525-cfee-225f-940c-78d646484c6d@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