From: Alex Williamson <alex.williamson@redhat.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
kvm@vger.kernel.org, Yishai Hadas <yishaih@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Kevin Tian <kevin.tian@intel.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH vfio-next 0/3] mlx5 VFIO PCI DMA conversion
Date: Tue, 20 May 2025 09:39:56 -0600 [thread overview]
Message-ID: <20250520093956.3856d75d.alex.williamson@redhat.com> (raw)
In-Reply-To: <cover.1747747694.git.leon@kernel.org>
On Tue, 20 May 2025 16:46:29 +0300
Leon Romanovsky <leon@kernel.org> wrote:
> Hi Alex,
>
> This series presents subset of new DMA-API patchset [1] specific
> for VFIO subsystem, with some small changes:
> 1. Change commit message in first patch.
> 2. Removed WARN_ON_ONCE DMA_NONE checks from third patch.
>
> ------------------------------------------------------------------
> It is based on Marek's dma-mapping-for-6.16-two-step-api branch, so merging
> now will allow us to reduce possible rebase errors in mlx5 vfio code and give
> enough time to start to work on second driver conversion. Such conversion will
> allow us to generalize the API for VFIO kernel drivers, in similar way that
> was done for RDMA, HMM and block layers.
>
> Thanks
>
> [1] [PATCH v10 00/24] Provide a new two step DMA mapping API
> https://lore.kernel.org/all/cover.1745831017.git.leon@kernel.org/
>
> Leon Romanovsky (3):
> vfio/mlx5: Explicitly use number of pages instead of allocated length
> vfio/mlx5: Rewrite create mkey flow to allow better code reuse
> vfio/mlx5: Enable the DMA link API
>
> drivers/vfio/pci/mlx5/cmd.c | 371 +++++++++++++++++------------------
> drivers/vfio/pci/mlx5/cmd.h | 35 ++--
> drivers/vfio/pci/mlx5/main.c | 87 ++++----
> 3 files changed, 235 insertions(+), 258 deletions(-)
Applied to vfio next branch for v6.16. Thanks,
Alex
prev parent reply other threads:[~2025-05-20 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 13:46 [PATCH vfio-next 0/3] mlx5 VFIO PCI DMA conversion Leon Romanovsky
2025-05-20 13:46 ` [PATCH vfio-next 1/3] vfio/mlx5: Explicitly use number of pages instead of allocated length Leon Romanovsky
2025-05-20 13:46 ` [PATCH vfio-next 2/3] vfio/mlx5: Rewrite create mkey flow to allow better code reuse Leon Romanovsky
2025-05-20 13:46 ` [PATCH vfio-next 3/3] vfio/mlx5: Enable the DMA link API Leon Romanovsky
2025-05-20 14:13 ` [PATCH vfio-next 0/3] mlx5 VFIO PCI DMA conversion Yishai Hadas
2025-05-20 15:39 ` Alex Williamson [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=20250520093956.3856d75d.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.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).