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 18:48:19 +0100	[thread overview]
Message-ID: <20250915174819.GA320514@horms.kernel.org> (raw)
In-Reply-To: <20250915081640.6d86ff6f@kernel.org>

On Mon, Sep 15, 2025 at 08:16:40AM -0700, Jakub Kicinski wrote:
> On Mon, 15 Sep 2025 10:58:46 +0100 Simon Horman wrote:
> > 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?
> 
> Fair, will add. I wasn't sure how to concisely include this.
> Ownership is kinda like the 0-th heartbeat in my mind..

Yeah, it was a bit of a nit pick.

> 
> > > 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?
> 
> Yes, sorry..
> 
> > > +	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?
> 
> ack!
> 
> Thanks for reviews!

Thanks. I did look over the rest of the series, and it looked good do me.
I'll plan to look over v2 too.

  reply	other threads:[~2025-09-15 17:48 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
2025-09-15 15:16     ` Jakub Kicinski
2025-09-15 17:48       ` Simon Horman [this message]
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=20250915174819.GA320514@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).