public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: [PATCH rdma-next V3 02/10] IB/mlx5: Fix decision on using MAD_IFC
Date: Fri, 11 Mar 2016 22:58:35 +0200	[thread overview]
Message-ID: <1457729923-4526-3-git-send-email-eli@mellanox.com> (raw)
In-Reply-To: <1457729923-4526-1-git-send-email-eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Fix the condition that dictates when MAD_IFC should be used. According
to firmware specifications, MAD_IFC commands must be used only if the
ib_virt capability is off.

Signed-off-by: Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Reviewed-by: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
---
 drivers/infiniband/hw/mlx5/main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/infiniband/hw/mlx5/main.c b/drivers/infiniband/hw/mlx5/main.c
index 7e89a547bf34..79ee6997daa2 100644
--- a/drivers/infiniband/hw/mlx5/main.c
+++ b/drivers/infiniband/hw/mlx5/main.c
@@ -283,7 +283,7 @@ __be16 mlx5_get_roce_udp_sport(struct mlx5_ib_dev *dev, u8 port_num,
 
 static int mlx5_use_mad_ifc(struct mlx5_ib_dev *dev)
 {
-	return !dev->mdev->issi;
+	return !MLX5_CAP_GEN(dev->mdev, ib_virt);
 }
 
 enum {
-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-03-11 20:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 20:58 [PATCH rdma-next V3 00/10] IB SR-IOV support Eli Cohen
     [not found] ` <1457729923-4526-1-git-send-email-eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-03-11 20:58   ` [PATCH rdma-next V3 01/10] net/core: Add support for configuring VF GUIDs Eli Cohen
     [not found]     ` <1457729923-4526-2-git-send-email-eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-03-13 13:44       ` Or Gerlitz
2016-03-11 20:58   ` Eli Cohen [this message]
2016-03-11 20:58   ` [PATCH rdma-next V3 03/10] IB/core: Add subnet prefix to port info Eli Cohen
2016-03-11 20:58   ` [PATCH rdma-next V3 04/10] IB/core: Support accessing SA in virtualized environment Eli Cohen
2016-03-11 20:58   ` [PATCH rdma-next V3 05/10] IB/core: Add interfaces to control VF attributes Eli Cohen
2016-03-11 20:58   ` [PATCH rdma-next V3 06/10] IB/ipoib: Add ndo operations for configuring VFs Eli Cohen
2016-03-11 20:58   ` [PATCH rdma-next V3 07/10] net/mlx5_core: Add VF param when querying vport counter Eli Cohen
2016-03-11 20:58   ` [PATCH rdma-next V3 08/10] net/mlx5_core: Implement modify HCA vport command Eli Cohen
2016-03-11 20:58   ` [PATCH rdma-next V3 09/10] IB/mlx5: Implement callbacks for manipulating VFs Eli Cohen
2016-03-11 20:58   ` [PATCH rdma-next V3 10/10] IB/ipoib: Allow mcast packets from other VFs Eli Cohen
2016-03-16 16:33   ` [PATCH rdma-next V3 00/10] IB SR-IOV support Eli Cohen

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=1457729923-4526-3-git-send-email-eli@mellanox.com \
    --to=eli-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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