From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/2] vdpa/mlx5: Fixes for ASID handling
Date: Thu, 10 Aug 2023 04:54:19 -0400 [thread overview]
Message-ID: <20230810045328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230802171231.11001-1-dtatulea@nvidia.com>
On Wed, Aug 02, 2023 at 08:12:16PM +0300, Dragos Tatulea wrote:
> This patch series is based on Eugenio's fix for handling CVQs in
> a different ASID [0].
>
> The first patch is the actual fix.
>
> The next 2 patches are fixing a possible issue that I found while
> implementing patch 1. The patches are ordered like this for clarity.
>
> [0] https://lore.kernel.org/lkml/20230112142218.725622-1-eperezma@redhat.com/
So what are we doing with this patchset? If we are merging anything
for this release it has to happen now.
> Dragos Tatulea (1):
> vdpa/mlx5: Fix mr->initialized semantics
>
> Eugenio Pérez (1):
> vdpa/mlx5: Delete control vq iotlb in destroy_mr only when necessary
>
> drivers/vdpa/mlx5/core/mlx5_vdpa.h | 2 +
> drivers/vdpa/mlx5/core/mr.c | 97 +++++++++++++++++++++---------
> drivers/vdpa/mlx5/net/mlx5_vnet.c | 4 +-
> 3 files changed, 74 insertions(+), 29 deletions(-)
>
> --
> 2.41.0
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/2] vdpa/mlx5: Fixes for ASID handling
Date: Thu, 10 Aug 2023 04:54:19 -0400 [thread overview]
Message-ID: <20230810045328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230802171231.11001-1-dtatulea@nvidia.com>
On Wed, Aug 02, 2023 at 08:12:16PM +0300, Dragos Tatulea wrote:
> This patch series is based on Eugenio's fix for handling CVQs in
> a different ASID [0].
>
> The first patch is the actual fix.
>
> The next 2 patches are fixing a possible issue that I found while
> implementing patch 1. The patches are ordered like this for clarity.
>
> [0] https://lore.kernel.org/lkml/20230112142218.725622-1-eperezma@redhat.com/
So what are we doing with this patchset? If we are merging anything
for this release it has to happen now.
> Dragos Tatulea (1):
> vdpa/mlx5: Fix mr->initialized semantics
>
> Eugenio Pérez (1):
> vdpa/mlx5: Delete control vq iotlb in destroy_mr only when necessary
>
> drivers/vdpa/mlx5/core/mlx5_vdpa.h | 2 +
> drivers/vdpa/mlx5/core/mr.c | 97 +++++++++++++++++++++---------
> drivers/vdpa/mlx5/net/mlx5_vnet.c | 4 +-
> 3 files changed, 74 insertions(+), 29 deletions(-)
>
> --
> 2.41.0
next prev parent reply other threads:[~2023-08-10 8:54 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 17:12 [PATCH 0/2] vdpa/mlx5: Fixes for ASID handling Dragos Tatulea via Virtualization
2023-08-02 17:12 ` Dragos Tatulea
2023-08-02 17:12 ` [PATCH 1/2] vdpa/mlx5: Fix mr->initialized semantics Dragos Tatulea via Virtualization
2023-08-02 17:12 ` Dragos Tatulea
2023-08-03 8:03 ` Jason Wang
2023-08-03 8:03 ` Jason Wang
2023-08-03 11:40 ` Dragos Tatulea via Virtualization
2023-08-03 11:40 ` Dragos Tatulea
2023-08-08 2:57 ` Jason Wang
2023-08-08 2:57 ` Jason Wang
2023-08-08 7:24 ` Dragos Tatulea via Virtualization
2023-08-08 7:24 ` Dragos Tatulea
2023-08-09 1:42 ` Jason Wang
2023-08-09 1:42 ` Jason Wang
2023-08-14 14:15 ` Dragos Tatulea via Virtualization
2023-08-14 14:15 ` Dragos Tatulea
2023-08-15 1:28 ` Jason Wang
2023-08-15 1:28 ` Jason Wang
2023-08-03 17:57 ` Si-Wei Liu
2023-08-03 17:57 ` Si-Wei Liu
2023-08-08 3:00 ` Jason Wang
2023-08-08 3:00 ` Jason Wang
2023-08-08 22:58 ` Si-Wei Liu
2023-08-08 22:58 ` Si-Wei Liu
2023-08-09 6:52 ` Jason Wang
2023-08-09 6:52 ` Jason Wang
2023-08-10 0:40 ` Si-Wei Liu
2023-08-10 0:40 ` Si-Wei Liu
2023-08-10 3:10 ` Jason Wang
2023-08-10 3:10 ` Jason Wang
2023-08-10 22:20 ` Si-Wei Liu
2023-08-10 22:20 ` Si-Wei Liu
2023-08-14 2:59 ` Jason Wang
2023-08-14 2:59 ` Jason Wang
2023-08-15 1:43 ` [PATCH RFC 0/4] vdpa: decouple reset of iotlb mapping from device reset Si-Wei Liu
2023-08-15 1:43 ` Si-Wei Liu
2023-08-15 1:43 ` [PATCH RFC 1/4] vdpa: introduce .reset_map operation callback Si-Wei Liu
2023-08-15 1:43 ` Si-Wei Liu
2023-08-15 2:21 ` Jason Wang
2023-08-15 2:21 ` Jason Wang
2023-08-15 19:49 ` Si-Wei Liu
2023-08-15 19:49 ` Si-Wei Liu
2023-08-16 1:55 ` Jason Wang
2023-08-16 1:55 ` Jason Wang
2023-08-17 0:05 ` Si-Wei Liu
2023-08-17 0:05 ` Si-Wei Liu
2023-08-17 15:28 ` Eugenio Perez Martin
2023-08-21 22:31 ` Si-Wei Liu
2023-08-21 22:31 ` Si-Wei Liu
2023-08-15 1:43 ` [PATCH RFC 2/4] vdpa/mlx5: implement .reset_map driver op Si-Wei Liu
2023-08-15 1:43 ` Si-Wei Liu
2023-08-15 8:26 ` Dragos Tatulea via Virtualization
2023-08-15 8:26 ` Dragos Tatulea
2023-08-15 23:11 ` Si-Wei Liu
2023-08-15 23:11 ` Si-Wei Liu
2023-08-15 1:43 ` [PATCH RFC 3/4] vhost-vdpa: should restore 1:1 dma mapping before detaching driver Si-Wei Liu
2023-08-15 1:43 ` Si-Wei Liu
2023-08-15 2:32 ` Jason Wang
2023-08-15 2:32 ` Jason Wang
2023-08-15 23:09 ` Si-Wei Liu
2023-08-15 23:09 ` Si-Wei Liu
2023-08-15 1:43 ` [PATCH RFC 4/4] vhost-vdpa: introduce IOTLB_PERSIST backend feature bit Si-Wei Liu
2023-08-15 1:43 ` Si-Wei Liu
2023-08-15 2:25 ` Jason Wang
2023-08-15 2:25 ` Jason Wang
2023-08-15 22:30 ` Si-Wei Liu
2023-08-15 22:30 ` Si-Wei Liu
2023-08-16 1:48 ` Jason Wang
2023-08-16 1:48 ` Jason Wang
2023-08-16 23:43 ` Si-Wei Liu
2023-08-16 23:43 ` Si-Wei Liu
2023-08-22 8:54 ` Jason Wang
2023-08-22 8:54 ` Jason Wang
2023-08-28 23:46 ` Si-Wei Liu
2023-08-28 23:46 ` Si-Wei Liu
2023-08-02 17:12 ` [PATCH 2/2] vdpa/mlx5: Delete control vq iotlb in destroy_mr only when necessary Dragos Tatulea via Virtualization
2023-08-02 17:12 ` Dragos Tatulea
2023-08-10 8:54 ` Michael S. Tsirkin [this message]
2023-08-10 8:54 ` [PATCH 0/2] vdpa/mlx5: Fixes for ASID handling Michael S. Tsirkin
2023-08-10 8:59 ` Jason Wang
2023-08-10 8:59 ` Jason Wang
2023-08-10 9:04 ` Dragos Tatulea via Virtualization
2023-08-10 9:04 ` Dragos Tatulea
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=20230810045328-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.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.