From: Doug Ledford <dledford@redhat.com>
To: Leon Romanovsky <leon@kernel.org>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Artemy Kovalyov <artemyko@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next 0/7] Enrich DEVX support
Date: Tue, 04 Dec 2018 14:02:01 -0500 [thread overview]
Message-ID: <95c8a200842de2a78af89ad2d5c051db0577fdfe.camel@redhat.com> (raw)
In-Reply-To: <20181126062838.5907-1-leon@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3367 bytes --]
On Mon, 2018-11-26 at 08:28 +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> From Yishai,
> -----------------------------------
> This series enriches DEVX support in few aspects: it enables interoperability
> between DEVX and verbs and improves mechanism for controlling privileged DEVX
> commands.
>
> The first patch updates mlx5 ifc file.
>
> Next 3 patches enable modifying and querying verbs objects via the DEVX
> interface.
>
> To achieve that the core layer introduced the 'UVERBS_IDR_ANY_OBJECT' type
> to match any IDR object. Once it's used by some driver's method, the
> infrastructure skips checking for the IDR type and it becomes the driver
> handler responsibility.
>
> The DEVX methods of modify and query were changed to get any object type via
> the 'UVERBS_IDR_ANY_OBJECT' mechanism. The type checking is done per object as
> part of the driver code.
>
> The next 3 patches introduce more robust mechanism for controlling privileged
> DEVX commands. The responsibility to block/allow per command was moved to be
> done in the firmware based on the UID credentials that the driver reports upon
> user context creation. This enables more granularity per command based on the
> device security model and the user credentials.
>
> In addition, by introducing a valid range for 'general commands' we prevent the
> need to touch the driver's code any time that a new future command will be
> added.
>
> The last patch fixes the XRC verbs flow once a DEVX context is used. This is
> needed as XRCD is some shared kernel resource and as such a kernel UID (=0)
> should be used in its related resources.
>
> Thanks
>
> Yishai Hadas (7):
> net/mlx5: Update mlx5_ifc with DEVX UCTX capabilities bits
> IB/core: Introduce UVERBS_IDR_ANY_OBJECT
> IB/core: Enable getting an object type from a given uobject
> IB/mlx5: Enable modify and query verbs objects via DEVX
> IB/mlx5: Enforce DEVX privilege by firmware
> IB/mlx5: Update the supported DEVX commands
> IB/mlx5: Allow XRC usage via verbs in DEVX context
>
> drivers/infiniband/core/rdma_core.c | 27 +++--
> drivers/infiniband/core/rdma_core.h | 21 ++--
> drivers/infiniband/core/uverbs_uapi.c | 10 +-
> drivers/infiniband/hw/mlx5/devx.c | 142 ++++++++++++++++++++++----
> drivers/infiniband/hw/mlx5/main.c | 4 +-
> drivers/infiniband/hw/mlx5/mlx5_ib.h | 6 +-
> drivers/infiniband/hw/mlx5/qp.c | 12 +--
> drivers/infiniband/hw/mlx5/srq.c | 2 +-
> include/linux/mlx5/mlx5_ifc.h | 26 ++++-
> include/rdma/uverbs_ioctl.h | 6 ++
> include/rdma/uverbs_std_types.h | 12 +++
> 11 files changed, 215 insertions(+), 53 deletions(-)
>
> --
> 2.19.1
>
Hi Leon,
I've put this into my wip/dl-for-next branch. Because it pulled in the
mlx5-next tree (which was significant because the patch we wanted was at
the tip and a whole slew of other patches were before it), the changeset
for this patch looks much bigger. And it had the merge conflict you
mentioned. You might want to double check my work before it gets moved
over to the official for-next branch.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-04 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 6:28 [PATCH rdma-next 0/7] Enrich DEVX support Leon Romanovsky
2018-11-26 6:28 ` [PATCH mlx5-next 1/7] net/mlx5: Update mlx5_ifc with DEVX UCTX capabilities bits Leon Romanovsky
2018-12-03 18:32 ` Doug Ledford
2018-12-04 7:56 ` Leon Romanovsky
2018-11-26 6:28 ` [PATCH rdma-next 2/7] IB/core: Introduce UVERBS_IDR_ANY_OBJECT Leon Romanovsky
2018-11-26 6:28 ` [PATCH rdma-next 3/7] IB/core: Enable getting an object type from a given uobject Leon Romanovsky
2018-11-26 6:28 ` [PATCH rdma-next 4/7] IB/mlx5: Enable modify and query verbs objects via DEVX Leon Romanovsky
2018-11-26 6:28 ` [PATCH rdma-next 5/7] IB/mlx5: Enforce DEVX privilege by firmware Leon Romanovsky
2018-11-26 6:28 ` [PATCH rdma-next 6/7] IB/mlx5: Update the supported DEVX commands Leon Romanovsky
2018-11-26 6:28 ` [PATCH rdma-next 7/7] IB/mlx5: Allow XRC usage via verbs in DEVX context Leon Romanovsky
2018-12-04 19:02 ` Doug Ledford [this message]
2018-12-04 19:15 ` [PATCH rdma-next 0/7] Enrich DEVX support Jason Gunthorpe
2018-12-04 19:45 ` Doug Ledford
2018-12-04 20:34 ` Leon Romanovsky
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=95c8a200842de2a78af89ad2d5c051db0577fdfe.camel@redhat.com \
--to=dledford@redhat.com \
--cc=artemyko@mellanox.com \
--cc=jgg@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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;
as well as URLs for NNTP newsgroup(s).