From: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next 3/5] ice: add ability to query/set FW log level and resolution
Date: Thu, 8 Dec 2022 16:00:02 -0800 [thread overview]
Message-ID: <08c5fa23-89ca-65e3-3f6c-1d5462fa56c9@intel.com> (raw)
In-Reply-To: <b7626585-15e1-0458-5585-a85801c9d79e@intel.com>
On 11/30/2022 4:39 PM, Tony Nguyen wrote:
> On 11/28/2022 1:47 PM, Paul M Stillwell Jr wrote:
>> The E8xx has the ability to change the FW log level and
>> the granularity at which the logs get output. Enable
>> the ability to see what the current values are and to
>> change them.
>>
>> Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
>> ---
>> .../net/ethernet/intel/ice/ice_adminq_cmd.h | 4 +
>> drivers/net/ethernet/intel/ice/ice_common.c | 4 +-
>> drivers/net/ethernet/intel/ice/ice_devlink.c | 142 ++++++++-
>> drivers/net/ethernet/intel/ice/ice_fwlog.c | 277 ++++++++++++++++++
>> drivers/net/ethernet/intel/ice/ice_fwlog.h | 5 +
>> drivers/net/ethernet/intel/ice/ice_type.h | 1 +
>> 6 files changed, 429 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h
>> b/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h
>> index d0026161a2b4..8fa18bc5d441 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h
>> +++ b/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h
>> @@ -2406,7 +2406,11 @@ enum ice_adminq_opc {
>> /* Standalone Commands/Events */
>> ice_aqc_opc_event_lan_overflow = 0x1001,
>> + /* FW Logging Commands */
>
> nit: As this seperator was removed from patch 1 and the first command in
> patch 2. This comment seems to fit better there. Also retaining the new
> line between the op and the FW logging group would be nice.
>
>> + 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,
>> };
>> #endif /* _ICE_ADMINQ_CMD_H_ */
>> diff --git a/drivers/net/ethernet/intel/ice/ice_common.c
>> b/drivers/net/ethernet/intel/ice/ice_common.c
>> index ecdc1ebb45d5..0b3adac13c66 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_common.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_common.c
>> @@ -879,7 +879,9 @@ int ice_init_hw(struct ice_hw *hw)
>> if (status)
>> goto err_unroll_cqinit;
>> - ice_fwlog_set_support_ena(hw);
>> + status = ice_fwlog_init(hw);
>> + if (status)
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Error initializing FW logging:
>> %d\n", status);
>> status = ice_clear_pf_cfg(hw);
>> if (status)
>> diff --git a/drivers/net/ethernet/intel/ice/ice_devlink.c
>> b/drivers/net/ethernet/intel/ice/ice_devlink.c
>> index 8843ff492f7f..ca67f2741f83 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_devlink.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_devlink.c
>> @@ -1488,6 +1488,8 @@ enum ice_devlink_param_id {
>> ICE_DEVLINK_PARAM_ID_BASE = DEVLINK_PARAM_GENERIC_ID_MAX,
>> ICE_DEVLINK_PARAM_ID_FWLOG_SUPPORTED,
>> ICE_DEVLINK_PARAM_ID_FWLOG_ENABLED,
>> + ICE_DEVLINK_PARAM_ID_FWLOG_LEVEL,
>> + ICE_DEVLINK_PARAM_ID_FWLOG_RESOLUTION,
>> };
>> static int
>> @@ -1530,8 +1532,121 @@ static int
>> ice_devlink_fwlog_enabled_set(struct devlink *devlink, u32 id,
>> struct devlink_param_gset_ctx *ctx)
>> {
>> - /* set operation is unsupported at this time */
>> - return -EOPNOTSUPP;
>> + struct ice_pf *pf = devlink_priv(devlink);
>> + struct ice_hw *hw = &pf->hw;
>> + int status;
>> +
>> + /* only support fw log commands on PF 0 */
>> + if (hw->bus.func)
>> + return -EOPNOTSUPP;
>> +
>> + if (hw->fwlog_ena == ctx->val.vbool)
>> + return 0;
>> +
>> + hw->fwlog_ena = ctx->val.vbool;
>> +
>> + if (hw->fwlog_ena)
>> + hw->fwlog_cfg.options |= ICE_FWLOG_OPTION_ARQ_ENA;
>> + else
>> + hw->fwlog_cfg.options &= ~ICE_FWLOG_OPTION_ARQ_ENA;
>> +
>> + /* send the cfg to FW and register for events */
>> + status = ice_fwlog_set(hw, &hw->fwlog_cfg);
>> + if (status)
>> + return status;
>> +
>> + if (hw->fwlog_ena) {
>> + status = ice_fwlog_register(hw);
>> + if (status)
>> + return status;
>> + } else {
>> + status = ice_fwlog_unregister(hw);
>> + if (status)
>> + return status;
>> + }
>> +
>> + return 0;
>> +}
>> +
>> +static int
>> +ice_devlink_fwlog_level_get(struct devlink *devlink, u32 id,
>> + struct devlink_param_gset_ctx *ctx)
>> +{
>> + struct ice_pf *pf = devlink_priv(devlink);
>> +
>> + /* only support fw log commands on PF 0 */
>> + if (pf->hw.bus.func)
>> + return -EOPNOTSUPP;
>> +
>> + /* all the log levels are the same so pick the first one */
>> + ctx->val.vu8 = pf->hw.fwlog_cfg.module_entries[0].log_level;
>
> Since they are all the same, would it make sense to store it in the
> config and pull the value from there instead of duplicating it for each
> entry?
>
I don't think so. They have to all be stored in the config because you
have to write them all out when you write the config. It makes sense to
me to keep them all in the config and read one of them instead of having
2 places with the value and possibly having a bug because they are out
of sync.
If I'm misundersstanding your comment then let me know.
>> +
>> + return 0;
>> +}
>> +
>> +static int
>> +ice_devlink_fwlog_level_set(struct devlink *devlink, u32 id,
>> + struct devlink_param_gset_ctx *ctx)
>> +{
>> + struct ice_pf *pf = devlink_priv(devlink);
>> + struct ice_fwlog_cfg *cfg;
>> + u8 i;
>> +
>> + if (pf->hw.bus.func)
>> + return -EOPNOTSUPP;
>> +
>> + if (ctx->val.vu8 >= ICE_FWLOG_LEVEL_INVALID) {
>> + dev_err(ice_pf_to_dev(pf), "Log level is greater than
>> allowed! %d\n",
>> + ctx->val.vu8);
>> + return -EINVAL;
>> + }
>> +
>> + cfg = &pf->hw.fwlog_cfg;
>> +
>> + /* update the log level for all modules to the same thing. this gets
>> + * written to the FW when the user says enable logging
>> + */
>> + for (i = 0; i < ICE_AQC_FW_LOG_ID_MAX; i++)
>> + cfg->module_entries[i].log_level = ctx->val.vu8;
>> +
>> + return 0;
>> +}
>> +
>> +static int
>> +ice_devlink_fwlog_resolution_get(struct devlink *devlink, u32 id,
>> + struct devlink_param_gset_ctx *ctx)
>> +{
>> + struct ice_pf *pf = devlink_priv(devlink);
>> +
>> + /* only support fw log commands on PF 0 */
>> + if (pf->hw.bus.func)
>> + return -EOPNOTSUPP;
>> +
>> + ctx->val.vu8 = pf->hw.fwlog_cfg.log_resolution;
>> +
>> + return 0;
>> +}
>> +
>> +static int
>> +ice_devlink_fwlog_resolution_set(struct devlink *devlink, u32 id,
>> + struct devlink_param_gset_ctx *ctx)
>> +{
>> + struct ice_pf *pf = devlink_priv(devlink);
>> +
>> + /* only support fw log commands on PF 0 */
>> + if (pf->hw.bus.func)
>> + return -EOPNOTSUPP;
>> +
>> + if (ctx->val.vu8 < ICE_AQC_FW_LOG_MIN_RESOLUTION ||
>> + ctx->val.vu8 > ICE_AQC_FW_LOG_MAX_RESOLUTION) {
>> + dev_err(ice_pf_to_dev(pf), "Log resolution is not allowed!
>> Should be between 1 - 128: %d\n",
>> + ctx->val.vu8);
>> + return -EINVAL;
>> + }
>> +
>> + pf->hw.fwlog_cfg.log_resolution = ctx->val.vu8;
>> +
>> + return 0;
>> }
>> static const struct devlink_param ice_devlink_params[] = {
>> @@ -1562,6 +1677,18 @@ static const struct devlink_param
>> ice_devlink_params[] = {
>> ice_devlink_fwlog_enabled_get,
>> ice_devlink_fwlog_enabled_set,
>> NULL),
>> + DEVLINK_PARAM_DRIVER(ICE_DEVLINK_PARAM_ID_FWLOG_LEVEL,
>> + "fwlog_level", DEVLINK_PARAM_TYPE_U8,
>> + BIT(DEVLINK_PARAM_CMODE_RUNTIME),
>> + ice_devlink_fwlog_level_get,
>> + ice_devlink_fwlog_level_set,
>> + NULL),
>> + DEVLINK_PARAM_DRIVER(ICE_DEVLINK_PARAM_ID_FWLOG_RESOLUTION,
>> + "fwlog_resolution", DEVLINK_PARAM_TYPE_U8,
>> + BIT(DEVLINK_PARAM_CMODE_RUNTIME),
>> + ice_devlink_fwlog_resolution_get,
>> + ice_devlink_fwlog_resolution_set,
>> + NULL),
>> };
>> static void ice_devlink_free(void *devlink_ptr)
>> @@ -1662,11 +1789,20 @@ int ice_devlink_register_params(struct ice_pf
>> *pf)
>> ICE_DEVLINK_PARAM_ID_FWLOG_SUPPORTED,
>> value);
>> - value.vbool = false;
>
> Is this on purpose?
>
Yes, the value doesn't change between the 2 calls so no need to set it a
second time.
>> devlink_param_driverinit_value_set(devlink,
>> ICE_DEVLINK_PARAM_ID_FWLOG_ENABLED,
>> value);
>> + value.vu8 = ICE_FWLOG_LEVEL_NORMAL;
>> + devlink_param_driverinit_value_set(devlink,
>> + ICE_DEVLINK_PARAM_ID_FWLOG_LEVEL,
>> + value);
>> +
>> + /* set the default value for the FW to pack 10 messages per AQ
>> event */
>> + value.vu8 = 10;
>> + devlink_param_driverinit_value_set(devlink,
>> + ICE_DEVLINK_PARAM_ID_FWLOG_RESOLUTION,
>> + value);
>> return 0;
>> }
>> diff --git a/drivers/net/ethernet/intel/ice/ice_fwlog.c
>> b/drivers/net/ethernet/intel/ice/ice_fwlog.c
>> index 67e670c62091..1174fd889307 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_fwlog.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_fwlog.c
>> @@ -4,6 +4,165 @@
>> #include "ice_common.h"
>> #include "ice_fwlog.h"
>> +/**
>> + * cache_cfg - Cache FW logging config
>> + * @hw: pointer to the HW structure
>> + * @cfg: config to cache
>> + */
>> +static void cache_cfg(struct ice_hw *hw, struct ice_fwlog_cfg *cfg)
>> +{
>> + hw->fwlog_cfg = *cfg;
>> +}
>> +
>> +/**
>> + * valid_module_entries - validate all the module entry IDs and log
>> levels
>> + * @hw: pointer to the HW structure
>> + * @entries: entries to validate
>> + * @num_entries: number of entries to validate
>> + */
>> +static bool
>> +valid_module_entries(struct ice_hw *hw, struct ice_fwlog_module_entry
>> *entries,
>> + u16 num_entries)
>> +{
>> + u16 i;
>> +
>> + if (!entries) {
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Null ice_fwlog_module_entry
>> array\n");
>> + return false;
>> + }
>> +
>> + if (!num_entries) {
>> + ice_debug(hw, ICE_DBG_FW_LOG, "num_entries must be non-zero\n");
>> + return false;
>> + }
>> +
>> + for (i = 0; i < num_entries; i++) {
>> + struct ice_fwlog_module_entry *entry = &entries[i];
>> +
>> + if (entry->module_id >= ICE_AQC_FW_LOG_ID_MAX) {
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Invalid module_id %u, max
>> valid module_id is %u\n",
>> + entry->module_id, ICE_AQC_FW_LOG_ID_MAX - 1);
>> + return false;
>> + }
>> +
>> + if (entry->log_level >= ICE_FWLOG_LEVEL_INVALID) {
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Invalid log_level %u, max
>> valid log_level is %u\n",
>> + entry->log_level,
>> + ICE_AQC_FW_LOG_ID_MAX - 1);
>> + return false;
>> + }
>> + }
>> +
>> + return true;
>> +}
>> +
>> +/**
>> + * valid_cfg - validate entire configuration
>> + * @hw: pointer to the HW structure
>> + * @cfg: config to validate
>> + */
>> +static bool valid_cfg(struct ice_hw *hw, struct ice_fwlog_cfg *cfg)
>> +{
>> + if (!cfg) {
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Null ice_fwlog_cfg\n");
>> + return false;
>> + }
>> +
>> + if (cfg->log_resolution < ICE_AQC_FW_LOG_MIN_RESOLUTION ||
>> + cfg->log_resolution > ICE_AQC_FW_LOG_MAX_RESOLUTION) {
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Unsupported log_resolution %u,
>> must be between %u and %u\n",
>> + cfg->log_resolution, ICE_AQC_FW_LOG_MIN_RESOLUTION,
>> + ICE_AQC_FW_LOG_MAX_RESOLUTION);
>> + return false;
>> + }
>> +
>> + if (!valid_module_entries(hw, cfg->module_entries,
>> + ICE_AQC_FW_LOG_ID_MAX))
>> + return false;
>> +
>> + return true;
>> +}
>> +
>> +/**
>> + * ice_fwlog_init - Initialize FW logging variables
>> + * @hw: pointer to the HW structure
>> + *
>> + * This function should be called on driver initialization during
>> + * ice_init_hw().
>> + */
>> +int ice_fwlog_init(struct ice_hw *hw)
>> +{
>> + int status;
>> +
>> + ice_fwlog_set_support_ena(hw);
>> +
>> + if (ice_fwlog_supported(hw)) {
>> + struct ice_fwlog_cfg *cfg;
>> +
>> + cfg = kzalloc(sizeof(*cfg), GFP_KERNEL);
>> + if (!cfg)
>> + return -ENOMEM;
>> +
>> + /* read the current config from the FW and store it */
>> + status = ice_fwlog_get(hw, cfg);
>> + if (status)
>> + return status;
>> + }
>> +
>> + return 0;
>> +}
>> +
>> +/**
>> + * ice_aq_fwlog_set - Set FW logging configuration AQ command (0xFF30)
>> + * @hw: pointer to the HW structure
>> + * @entries: entries to configure
>> + * @num_entries: number of @entries
>> + * @options: options from ice_fwlog_cfg->options structure
>> + * @log_resolution: logging resolution
>> + */
>> +static int
>> +ice_aq_fwlog_set(struct ice_hw *hw, struct ice_fwlog_module_entry
>> *entries,
>> + u16 num_entries, u16 options, u16 log_resolution)
>> +{
>> + struct ice_aqc_fw_log_cfg_resp *fw_modules;
>> + struct ice_aqc_fw_log *cmd;
>> + struct ice_aq_desc desc;
>> + int status;
>> + u16 i;
>> +
>> + fw_modules = kcalloc(num_entries, sizeof(*fw_modules), GFP_KERNEL);
>> + if (!fw_modules)
>> + return -ENOMEM;
>> +
>> + for (i = 0; i < num_entries; i++) {
>> + fw_modules[i].module_identifier =
>> + cpu_to_le16(entries[i].module_id);
>> + fw_modules[i].log_level = entries[i].log_level;
>> + }
>> +
>> + ice_fill_dflt_direct_cmd_desc(&desc, ice_aqc_opc_fw_logs_config);
>> + desc.flags |= cpu_to_le16(ICE_AQ_FLAG_RD);
>> +
>> + cmd = &desc.params.fw_log;
>> +
>> + cmd->cmd_flags = ICE_AQC_FW_LOG_CONF_SET_VALID;
>> + cmd->ops.cfg.log_resolution = cpu_to_le16(log_resolution);
>> + cmd->ops.cfg.mdl_cnt = cpu_to_le16(num_entries);
>> +
>> + if (options & ICE_FWLOG_OPTION_ARQ_ENA)
>> + cmd->cmd_flags |= ICE_AQC_FW_LOG_CONF_AQ_EN;
>> + if (options & ICE_FWLOG_OPTION_UART_ENA)
>> + cmd->cmd_flags |= ICE_AQC_FW_LOG_CONF_UART_EN;
>> +
>> + status = ice_aq_send_cmd(hw, &desc, fw_modules,
>> + sizeof(*fw_modules) * num_entries,
>> + NULL);
>> +
>> + kfree(fw_modules);
>> +
>> + return status;
>> +}
>> +
>> /**
>> * ice_fwlog_supported - Cached for whether FW supports FW logging
>> or not
>> * @hw: pointer to the HW structure
>> @@ -16,6 +175,99 @@ bool ice_fwlog_supported(struct ice_hw *hw)
>> return hw->fwlog_support_ena;
>> }
>> +/**
>> + * ice_fwlog_set - Set the firmware logging settings
>> + * @hw: pointer to the HW structure
>> + * @cfg: config used to set firmware logging
>> + *
>> + * This function should be called whenever the driver needs to set
>> the firmware
>> + * logging configuration. It can be called on initialization, reset,
>> or during
>> + * runtime.
>> + *
>> + * If the PF wishes to receive FW logging then it must register via
>> + * ice_fwlog_register. Note, that ice_fwlog_register does not need to
>> be called
>> + * for init.
>> + */
>> +int
>> +ice_fwlog_set(struct ice_hw *hw, struct ice_fwlog_cfg *cfg)
>
> This can fit on one line...
>
I went through the file and pulled all of them up that could be. Nice catch.
>> +{
>> + int status;
>> +
>> + if (!ice_fwlog_supported(hw))
>> + return -EOPNOTSUPP;
>> +
>> + if (!valid_cfg(hw, cfg))
>> + return -EINVAL;
>> +
>> + status = ice_aq_fwlog_set(hw, cfg->module_entries,
>> + ICE_AQC_FW_LOG_ID_MAX, cfg->options,
>> + cfg->log_resolution);
>> + if (!status)
>> + cache_cfg(hw, cfg);
>> +
>> + return status;
>> +}
>> +
>> +/**
>> + * ice_aq_fwlog_register - Register PF for firmware logging events
>> (0xFF31)
>> + * @hw: pointer to the HW structure
>> + * @reg: true to register and false to unregister
>> + */
>> +static int ice_aq_fwlog_register(struct ice_hw *hw, bool reg)
>> +{
>> + struct ice_aq_desc desc;
>> +
>> + ice_fill_dflt_direct_cmd_desc(&desc, ice_aqc_opc_fw_logs_register);
>> +
>> + if (reg)
>> + desc.params.fw_log.cmd_flags = ICE_AQC_FW_LOG_AQ_REGISTER;
>> +
>> + return ice_aq_send_cmd(hw, &desc, NULL, 0, NULL);
>> +}
>> +
>> +/**
>> + * ice_fwlog_register - Register the PF for firmware logging
>> + * @hw: pointer to the HW structure
>> + *
>> + * After this call the PF will start to receive firmware logging
>> based on the
>> + * configuration set in ice_fwlog_set.
>> + */
>> +int ice_fwlog_register(struct ice_hw *hw)
>> +{
>> + int status;
>> +
>> + if (!ice_fwlog_supported(hw))
>> + return -EOPNOTSUPP;
>> +
>> + status = ice_aq_fwlog_register(hw, true);
>> + if (status)
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Failed to register for
>> firmware logging events over ARQ\n");
>> + else
>> + hw->fwlog_cfg.options |= ICE_FWLOG_OPTION_IS_REGISTERED;
>> +
>> + return status;
>> +}
>> +
>> +/**
>> + * ice_fwlog_unregister - Unregister the PF from firmware logging
>> + * @hw: pointer to the HW structure
>> + */
>> +int ice_fwlog_unregister(struct ice_hw *hw)
>> +{
>> + int status;
>> +
>> + if (!ice_fwlog_supported(hw))
>> + return -EOPNOTSUPP;
>> +
>> + status = ice_aq_fwlog_register(hw, false);
>> + if (status)
>> + ice_debug(hw, ICE_DBG_FW_LOG, "Failed to unregister from
>> firmware logging events over ARQ\n");
>> + else
>> + hw->fwlog_cfg.options &= ~ICE_FWLOG_OPTION_IS_REGISTERED;
>> +
>> + return status;
>> +}
>> +
>> /**
>> * ice_aq_fwlog_get - Get the current firmware logging configuration
>> (0xFF32)
>> * @hw: pointer to the HW structure
>> @@ -115,3 +367,28 @@ void ice_fwlog_set_support_ena(struct ice_hw *hw)
>> kfree(cfg);
>> }
>> +
>> +/**
>> + * ice_fwlog_get - Get the firmware logging settings
>> + * @hw: pointer to the HW structure
>> + * @cfg: config to populate based on current firmware logging settings
>> + */
>> +int
>> +ice_fwlog_get(struct ice_hw *hw, struct ice_fwlog_cfg *cfg)
>
> and this one. Can you check that all the others are pulled up properly
> as well?
>
>> +{
>> + int status;
>> +
>> + if (!ice_fwlog_supported(hw))
>> + return -EOPNOTSUPP;
>> +
>> + if (!cfg)
>> + return -EINVAL;
>> +
>> + status = ice_aq_fwlog_get(hw, cfg);
>> + if (status)
>> + return status;
>> +
>> + cache_cfg(hw, cfg);
>> +
>> + return 0;
>> +}
>> diff --git a/drivers/net/ethernet/intel/ice/ice_fwlog.h
>> b/drivers/net/ethernet/intel/ice/ice_fwlog.h
>> index d7371253b8e5..66648c5ba92c 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_fwlog.h
>> +++ b/drivers/net/ethernet/intel/ice/ice_fwlog.h
>> @@ -48,4 +48,9 @@ struct ice_fwlog_cfg {
>> void ice_fwlog_set_support_ena(struct ice_hw *hw);
>> bool ice_fwlog_supported(struct ice_hw *hw);
>> +int ice_fwlog_init(struct ice_hw *hw);
>> +int ice_fwlog_set(struct ice_hw *hw, struct ice_fwlog_cfg *cfg);
>> +int ice_fwlog_get(struct ice_hw *hw, struct ice_fwlog_cfg *cfg);
>> +int ice_fwlog_register(struct ice_hw *hw);
>> +int ice_fwlog_unregister(struct ice_hw *hw);
>> #endif /* _ICE_FWLOG_H_ */
>> diff --git a/drivers/net/ethernet/intel/ice/ice_type.h
>> b/drivers/net/ethernet/intel/ice/ice_type.h
>> index 10b78faf0a32..c524179e79f0 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_type.h
>> +++ b/drivers/net/ethernet/intel/ice/ice_type.h
>> @@ -861,6 +861,7 @@ struct ice_hw {
>> u8 fw_patch; /* firmware patch version */
>> u32 fw_build; /* firmware build number */
>> + struct ice_fwlog_cfg fwlog_cfg;
>> bool fwlog_support_ena; /* does hardware support FW logging? */
>> bool fwlog_ena; /* currently logging? */
_______________________________________________
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-09 0:00 UTC|newest]
Thread overview: 21+ 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 [this message]
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 ` [Intel-wired-lan] [PATCH net-next 0/5] add v2 FW logging for ice driver Tony Nguyen
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=08c5fa23-89ca-65e3-3f6c-1d5462fa56c9@intel.com \
--to=paul.m.stillwell.jr@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
/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