From: Yishai Hadas <yishaih@dev.mellanox.co.il>
To: Benjamin Poirier <bpoirier@suse.de>
Cc: Amir Vadai <amirv@mellanox.com>, Ido Shamay <idos@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mlx4_core: Fix fallback from MSI-X to INTx
Date: Wed, 27 May 2015 12:43:04 +0300 [thread overview]
Message-ID: <556591A8.6050602@dev.mellanox.co.il> (raw)
In-Reply-To: <1432336346-20290-1-git-send-email-bpoirier@suse.de>
On 5/23/2015 2:12 AM, Benjamin Poirier wrote:
> The test in mlx4_load_one() to remove MLX4_FLAG_MSI_X expects mlx4_NOP() to
> fail with -EBUSY. It is also necessary to avoid the reset since the device
> is not fully reinitialized before calling mlx4_start_hca() a second time.
>
> Note that this will also affect mlx4_test_interrupts(), the only other user
> of MLX4_CMD_NOP.
>
> Fixes: f5aef5a ("net/mlx4_core: Activate reset flow upon fatal command cases")
> Signed-off-by: Benjamin Poirier <bpoirier@suse.de>
> ---
> drivers/net/ethernet/mellanox/mlx4/cmd.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx4/cmd.c b/drivers/net/ethernet/mellanox/mlx4/cmd.c
> index 4f7dc04..529ef05 100644
> --- a/drivers/net/ethernet/mellanox/mlx4/cmd.c
> +++ b/drivers/net/ethernet/mellanox/mlx4/cmd.c
> @@ -714,8 +714,13 @@ static int mlx4_cmd_wait(struct mlx4_dev *dev, u64 in_param, u64 *out_param,
> msecs_to_jiffies(timeout))) {
> mlx4_warn(dev, "command 0x%x timed out (go bit not cleared)\n",
> op);
> - err = -EIO;
> - goto out_reset;
> + if (op == MLX4_CMD_NOP) {
> + err = -EBUSY;
> + goto out;
> + } else {
> + err = -EIO;
> + goto out_reset;
> + }
> }
>
> err = context->result;
>
It looks fine, a private case that should not trigger the reset flow.
prev parent reply other threads:[~2015-05-27 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 23:12 Benjamin Poirier
2015-05-27 9:43 ` Yishai Hadas [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=556591A8.6050602@dev.mellanox.co.il \
--to=yishaih@dev.mellanox.co.il \
--cc=amirv@mellanox.com \
--cc=bpoirier@suse.de \
--cc=idos@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=yishaih@mellanox.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
Powered by JetHome