From: Jacob Keller <jacob.e.keller@intel.com>
To: Harshitha Ramamurthy <hramamurthy@google.com>, <netdev@vger.kernel.org>
Cc: <joshwash@google.com>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <richardcochran@gmail.com>,
<jstultz@google.com>, <tglx@kernel.org>, <sboyd@kernel.org>,
<willemb@google.com>, <nktgrg@google.com>, <jfraker@google.com>,
<ziweixiao@google.com>, <maolson@google.com>,
<jordanrhee@google.com>, <thostet@google.com>,
<alok.a.tiwari@oracle.com>, <pkaligineedi@google.com>,
<horms@kernel.org>, <dwmw2@infradead.org>, <yyd@google.com>,
<jefrogers@google.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v6 1/3] gve: skip error logging for retryable AdminQ commands
Date: Thu, 7 May 2026 14:14:59 -0700 [thread overview]
Message-ID: <50d567e8-abce-48d4-b1c4-6ac0459382f2@intel.com> (raw)
In-Reply-To: <20260507211304.3046526-2-hramamurthy@google.com>
On 5/7/2026 2:13 PM, Harshitha Ramamurthy wrote:
> From: Jordan Rhee <jordanrhee@google.com>
>
> AdminQ commands may return -EAGAIN under certain transient conditions.
> These commands are intended to be retried by the driver, so logging
> a formal error to the system log is misleading and creates
> unnecessary noise.
>
> Modify the logging logic to skip the error message when the result
> is -EAGAIN, and move logging to dev_err_ratelimited() to avoid
> spamming the log.
>
Excellent!
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> Reviewed-by: Joshua Washington <joshwash@google.com>
> Signed-off-by: Jordan Rhee <jordanrhee@google.com>
> Signed-off-by: Harshitha Ramamurthy <hramamurthy@google.com>
> ---
> Changes in v4:
> - call out change to dev_err_ratelimited() in the commit message (Jacob Keller)
> - remove extra print when adminQ status is GVE_ADMINQ_COMMAND_UNSET (Jacob Keller)
> ---
> drivers/net/ethernet/google/gve/gve_adminq.c | 27 +++++++++++++++-----
> 1 file changed, 20 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/ethernet/google/gve/gve_adminq.c b/drivers/net/ethernet/google/gve/gve_adminq.c
> index 08587bf40ed4..a65b14835aa0 100644
> --- a/drivers/net/ethernet/google/gve/gve_adminq.c
> +++ b/drivers/net/ethernet/google/gve/gve_adminq.c
> @@ -416,16 +416,10 @@ static bool gve_adminq_wait_for_cmd(struct gve_priv *priv, u32 prod_cnt)
>
> static int gve_adminq_parse_err(struct gve_priv *priv, u32 status)
> {
> - if (status != GVE_ADMINQ_COMMAND_PASSED &&
> - status != GVE_ADMINQ_COMMAND_UNSET) {
> - dev_err(&priv->pdev->dev, "AQ command failed with status %d\n", status);
> - priv->adminq_cmd_fail++;
> - }
> switch (status) {
> case GVE_ADMINQ_COMMAND_PASSED:
> return 0;
> case GVE_ADMINQ_COMMAND_UNSET:
> - dev_err(&priv->pdev->dev, "parse_aq_err: err and status both unset, this should not be possible.\n");
> return -EINVAL;
> case GVE_ADMINQ_COMMAND_ERROR_ABORTED:
> case GVE_ADMINQ_COMMAND_ERROR_CANCELLED:
> @@ -455,6 +449,16 @@ static int gve_adminq_parse_err(struct gve_priv *priv, u32 status)
> }
> }
>
> +static bool gve_adminq_is_retryable(enum gve_adminq_opcodes opcode)
> +{
> + switch (opcode) {
> + case GVE_ADMINQ_REPORT_NIC_TIMESTAMP:
> + return true;
> + default:
> + return false;
> + }
> +}
> +
> /* Flushes all AQ commands currently queued and waits for them to complete.
> * If there are failures, it will return the first error.
> */
> @@ -482,9 +486,18 @@ static int gve_adminq_kick_and_wait(struct gve_priv *priv)
> cmd = &priv->adminq[i & priv->adminq_mask];
> status = be32_to_cpu(READ_ONCE(cmd->status));
> err = gve_adminq_parse_err(priv, status);
> - if (err)
> + if (err) {
> + enum gve_adminq_opcodes opcode =
> + be32_to_cpu(READ_ONCE(cmd->opcode));
> + priv->adminq_cmd_fail++;
> + if (!gve_adminq_is_retryable(opcode) || err != -EAGAIN)
> + dev_err_ratelimited(&priv->pdev->dev,
> + "AQ command %d failed with status %d\n",
> + opcode, status);
> +
> // Return the first error if we failed.
> return err;
> + }
> }
>
> return 0;
next prev parent reply other threads:[~2026-05-07 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 21:13 [PATCH net-next v6 0/3] gve: add support for PTP gettimex64 Harshitha Ramamurthy
2026-05-07 21:13 ` [PATCH net-next v6 1/3] gve: skip error logging for retryable AdminQ commands Harshitha Ramamurthy
2026-05-07 21:14 ` Jacob Keller [this message]
2026-05-10 4:31 ` Jordan Rhee
2026-05-07 21:13 ` [PATCH net-next v6 2/3] gve: make nic clock reads thread safe Harshitha Ramamurthy
2026-05-07 21:15 ` Jacob Keller
2026-05-07 21:13 ` [PATCH net-next v6 3/3] gve: implement PTP gettimex64 Harshitha Ramamurthy
2026-05-07 21:23 ` Jacob Keller
2026-05-08 17:43 ` Jordan Rhee
2026-05-08 21:53 ` Jacob Keller
2026-05-10 4:54 ` Jordan Rhee
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=50d567e8-abce-48d4-b1c4-6ac0459382f2@intel.com \
--to=jacob.e.keller@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jefrogers@google.com \
--cc=jfraker@google.com \
--cc=jordanrhee@google.com \
--cc=joshwash@google.com \
--cc=jstultz@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maolson@google.com \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=richardcochran@gmail.com \
--cc=sboyd@kernel.org \
--cc=tglx@kernel.org \
--cc=thostet@google.com \
--cc=willemb@google.com \
--cc=yyd@google.com \
--cc=ziweixiao@google.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