IB/mlx4: deprecate "failed to alloc bf reg" message from err to debug

This message is not an error, and qp creation continues
normally -- only without use of blueflame.

For VFs attached to VMs, KVM disables write combining, so
performance is better without BF in this case.  The host driver
therefore intentionally disables BF use for guests. (see upstream
kernel commit b91cb3ebcd).

The message notifying that BF is not available is therefore
deprecated from err to debug.

Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
(Ported from Mellanox OFED 2.4)

Signed-off-by: Mukesh Kacker <mukesh.kacker@oracle.com>

diff --git a/drivers/infiniband/hw/mlx4/qp.c b/drivers/infiniband/hw/mlx4/qp.c
index dc5bab3b94fc8ec954a598e8eefc756cb1c7f634..eb4057dd487c19bc08d73370f22422df8ad8aa94 100644 (file)
--- a/drivers/infiniband/hw/mlx4/qp.c
+++ b/drivers/infiniband/hw/mlx4/qp.c
@@ -792,8 +792,8 @@ static int create_qp_common(struct mlx4_ib_dev *dev, struct ib_pd *pd,
                if (qp->max_inline_data) {
                        err = mlx4_bf_alloc(dev->dev, &qp->bf, 0);
                        if (err) {
-                               pr_err("failed to allocate blue flame"
-                                      " register (%d)", err);
+                               pr_debug("failed to allocate blue flame"
+                                        " register (%d)", err);
                                qp->bf.uar = &dev->priv_uar;
                        }
                } else