All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Zhu Yanjun <yanjunz@mellanox.com>,
	Amir Vadai <amirv@mellanox.com>,
	Haggai Eran <haggaie@mellanox.com>,
	Kamal Heib <kamalh@mellanox.com>,
	linux-rdma@vger.kernel.org, Moni Shoua <monis@mellanox.com>
Subject: Re: [PATCH rdma-next] RDMA/rxe: Set default vendor ID
Date: Tue, 14 Apr 2020 16:00:10 -0300	[thread overview]
Message-ID: <20200414190010.GA11664@ziepe.ca> (raw)
In-Reply-To: <20200406173501.1466273-1-leon@kernel.org>

On Mon, Apr 06, 2020 at 08:35:01PM +0300, Leon Romanovsky wrote:
> From: Zhu Yanjun <yanjunz@mellanox.com>
> 
> The RXE driver doesn't set vendor_id and user space applications
> see zeros. This causes to pyverbs tests to fail with the following
> traceback, because the expectation is to have valid vendor_id.
> 
> Traceback (most recent call last):
>   File "tests/test_device.py", line 51, in test_query_device
>     self.verify_device_attr(attr)
>   File "tests/test_device.py", line 77, in verify_device_attr
>     assert attr.vendor_id != 0
> 
> In order to fix it, we will set vendor_id 0XFFFFFF, according
> to the IBTA v1.4 A3.3.1 VENDOR INFORMATION section.
> 
> """
> A vendor that produces a generic controller (i.e., one that supports a
> standard I/O protocol such as SRP), which does not have vendor specific
> device drivers, may use the value of 0xFFFFFF in the VendorID field.
> """
> 
> Before:
> "
> hca_id: rxe0
>         transport:                      InfiniBand (0)
>         fw_ver:                         0.0.0
>         node_guid:                      5054:00ff:feaa:5363
>         sys_image_guid:                 5054:00ff:feaa:5363
>         vendor_id:                      0x0000
> "
> 
> After:
> "
> hca_id: rxe0
>         transport:                      InfiniBand (0)
>         fw_ver:                         0.0.0
>         node_guid:                      5054:00ff:feaa:5363
>         sys_image_guid:                 5054:00ff:feaa:5363
>         vendor_id:                      0xffffff
> "
> 
> Fixes: 8700e3e7c485 ("Soft RoCE driver")
> Signed-off-by: Zhu Yanjun <yanjunz@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
>  drivers/infiniband/sw/rxe/rxe.c       | 1 +
>  drivers/infiniband/sw/rxe/rxe_param.h | 3 +++
>  2 files changed, 4 insertions(+)

Applied to for-next, thanks

Jason

      reply	other threads:[~2020-04-14 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 17:35 [PATCH rdma-next] RDMA/rxe: Set default vendor ID Leon Romanovsky
2020-04-14 19:00 ` Jason Gunthorpe [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=20200414190010.GA11664@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=amirv@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=haggaie@mellanox.com \
    --cc=kamalh@mellanox.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=monis@mellanox.com \
    --cc=yanjunz@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 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.