From: Saeed Mahameed <saeed@kernel.org>
To: Ganesh Goudar <ganeshgr@linux.ibm.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, moshe@nvidia.com,
leon@kernel.org, mahesh@linux.ibm.com, oohall@gmail.com
Subject: Re: [PATCH net] net/mlx5: Avoid MMIO when the error is detected
Date: Mon, 21 Aug 2023 13:51:56 -0700 [thread overview]
Message-ID: <ZOPObNv+GcdzRplA@x130> (raw)
In-Reply-To: <20230807083205.18557-1-ganeshgr@linux.ibm.com>
On 07 Aug 14:02, Ganesh Goudar wrote:
>When the drivers are notfied about the pci error, All
>the IO to the card must be stopped, Else the recovery would
>fail, Avoid memory-mapped IO until the device recovers
>from pci error.
>
>Signed-off-by: Ganesh Goudar <ganeshgr@linux.ibm.com>
>---
> drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c | 3 +++
> 1 file changed, 3 insertions(+)
>
>diff --git a/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c b/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
>index 932fbc843c69..010dee4eec14 100644
>--- a/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
>+++ b/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
>@@ -221,10 +221,13 @@ static void mlx5_timestamp_overflow(struct work_struct *work)
> clock = container_of(timer, struct mlx5_clock, timer);
> mdev = container_of(clock, struct mlx5_core_dev, clock);
>
>+ if (mdev->state == MLX5_DEVICE_STATE_INTERNAL_ERROR)
>+ goto out;
> write_seqlock_irqsave(&clock->lock, flags);
> timecounter_read(&timer->tc);
> mlx5_update_clock_info_page(mdev);
> write_sequnlock_irqrestore(&clock->lock, flags);
>+out:
> schedule_delayed_work(&timer->overflow_work, timer->overflow_period);
> }
>
Another version of this fix was already submitted and accepted:
https://patchwork.kernel.org/project/netdevbpf/patch/20230807212607.50883-10-saeed@kernel.org/
>--
>2.40.1
>
>
prev parent reply other threads:[~2023-08-21 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 8:32 [PATCH net] net/mlx5: Avoid MMIO when the error is detected Ganesh Goudar
2023-08-21 20:51 ` Saeed Mahameed [this message]
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=ZOPObNv+GcdzRplA@x130 \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=ganeshgr@linux.ibm.com \
--cc=leon@kernel.org \
--cc=mahesh@linux.ibm.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=oohall@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.