netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, alexanderduyck@fb.com,
	jacob.e.keller@intel.com
Subject: Re: [PATCH net-next 2/9] eth: fbnic: use fw uptime to detect fw crashes
Date: Mon, 15 Sep 2025 10:58:46 +0100	[thread overview]
Message-ID: <20250915095846.GO224143@horms.kernel.org> (raw)
In-Reply-To: <20250912201428.566190-3-kuba@kernel.org>

On Fri, Sep 12, 2025 at 01:14:21PM -0700, Jakub Kicinski wrote:
> Currently we only detect FW crashes when it stops responding
> to heartbeat messages. FW has a watchdog which will reset it
> in case of crashes. Use FW uptime sent in the heartbeat messages
> to detect that the watchdog has fired.

I see that the time sent in heartbeat messages is critical to this check.
But the time sent in ownership messages is also used, right?

> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
>  drivers/net/ethernet/meta/fbnic/fbnic.h    |  4 ++++
>  drivers/net/ethernet/meta/fbnic/fbnic_fw.h |  6 ++++++
>  drivers/net/ethernet/meta/fbnic/fbnic_fw.c | 15 ++++++++++++++-
>  3 files changed, 24 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/meta/fbnic/fbnic.h b/drivers/net/ethernet/meta/fbnic/fbnic.h
> index 311c7dda911a..09058d847729 100644
> --- a/drivers/net/ethernet/meta/fbnic/fbnic.h
> +++ b/drivers/net/ethernet/meta/fbnic/fbnic.h
> @@ -84,6 +84,10 @@ struct fbnic_dev {
>  	/* Local copy of hardware statistics */
>  	struct fbnic_hw_stats hw_stats;
>  
> +	/* Firmware time since boot in milliseconds */
> +	u64 firmware_time;
> +	u64 prev_firmware_time;
> +
>  	struct fbnic_fw_log fw_log;
>  };
>  
> diff --git a/drivers/net/ethernet/meta/fbnic/fbnic_fw.h b/drivers/net/ethernet/meta/fbnic/fbnic_fw.h
> index ec67b80809b0..c1de2793fa3d 100644
> --- a/drivers/net/ethernet/meta/fbnic/fbnic_fw.h
> +++ b/drivers/net/ethernet/meta/fbnic/fbnic_fw.h
> @@ -201,6 +201,12 @@ enum {
>  	FBNIC_FW_OWNERSHIP_MSG_MAX
>  };
>  
> +enum {
> +	FBNIC_FW_HEARTBEAT_UPTIME               = 0x0,
> +	FBNIC_FW_HEARTBEAT_NUMBER_OF_MESSAGES   = 0x1,
> +	FBNIC_FW_HEARTBEAT_MSG_MAX
> +};
> +
>  enum {
>  	FBNIC_FW_START_UPGRADE_ERROR		= 0x0,
>  	FBNIC_FW_START_UPGRADE_SECTION		= 0x1,
> diff --git a/drivers/net/ethernet/meta/fbnic/fbnic_fw.c b/drivers/net/ethernet/meta/fbnic/fbnic_fw.c
> index 6e580654493c..72f750eea055 100644
> --- a/drivers/net/ethernet/meta/fbnic/fbnic_fw.c
> +++ b/drivers/net/ethernet/meta/fbnic/fbnic_fw.c
> @@ -495,6 +495,11 @@ int fbnic_fw_xmit_ownership_msg(struct fbnic_dev *fbd, bool take_ownership)
>  
>  	fbd->last_heartbeat_request = req_time;
>  
> +	/* Set prev_firmware_time to 0 to avoid triggering firmware crash
> +	 * detection now that we received a response from firmware.
> +	 */

I'm having a bit of trouble understanding this comment.
Here we are sending an ownership message.
Have we (also) received a response from firmware?

> +	fbd->prev_firmware_time = 0;
> +
>  	/* Set heartbeat detection based on if we are taking ownership */
>  	fbd->fw_heartbeat_enabled = take_ownership;
>  
> @@ -671,6 +676,9 @@ static int fbnic_fw_parse_ownership_resp(void *opaque,
>  	/* Count the ownership response as a heartbeat reply */
>  	fbd->last_heartbeat_response = jiffies;
>  
> +	/* Capture firmware time for logging and firmware crash check */
> +	fbd->firmware_time = fta_get_uint(results, FBNIC_FW_HEARTBEAT_UPTIME);

Maybe FBNIC_FW_OWNERSHIP_UPTIME?

> +
>  	return 0;
>  }
>  
> @@ -685,6 +693,9 @@ static int fbnic_fw_parse_heartbeat_resp(void *opaque,
>  
>  	fbd->last_heartbeat_response = jiffies;
>  
> +	/* Capture firmware time for logging and firmware crash check */
> +	fbd->firmware_time = fta_get_uint(results, FBNIC_FW_HEARTBEAT_UPTIME);
> +
>  	return 0;
>  }

...

  reply	other threads:[~2025-09-15  9:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 20:14 [PATCH net-next 0/9] eth: fbnic: add devlink health support for FW crashes and OTP mem corruptions Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 1/9] eth: fbnic: make fbnic_fw_log_write() parameter const Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 2/9] eth: fbnic: use fw uptime to detect fw crashes Jakub Kicinski
2025-09-15  9:58   ` Simon Horman [this message]
2025-09-15 15:16     ` Jakub Kicinski
2025-09-15 17:48       ` Simon Horman
2025-09-12 20:14 ` [PATCH net-next 3/9] eth: fbnic: factor out clearing the action TCAM Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 4/9] eth: fbnic: reprogram TCAMs after FW crash Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 5/9] eth: fbnic: support allocating FW completions with extra space Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 6/9] eth: fbnic: support FW communication for core dump Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 7/9] eth: fbnic: add FW health reporter Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 8/9] eth: fbnic: report FW uptime in health diagnose Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 9/9] eth: fbnic: add OTP health reporter Jakub Kicinski

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=20250915095846.GO224143@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=alexanderduyck@fb.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).