From: Dragos Tatulea <dtatulea@nvidia.com>
To: "Michael S . Tsirkin" <mst@redhat.com>,
<virtualization@lists.linux.dev>,
Si-Wei Liu <si-wei.liu@oracle.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
Jason Wang <jasowang@redhat.com>,
Eugenio Perez Martin <eperezma@redhat.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Gal Pressman <gal@nvidia.com>,
Parav Pandit <parav@nvidia.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: [PATCH vhost 0/2] vdpa/mlx5: Iova mapping related fixes
Date: Mon, 21 Oct 2024 16:40:38 +0300 [thread overview]
Message-ID: <20241021134040.975221-1-dtatulea@nvidia.com> (raw)
Here are 2 fixes from Si-Wei:
- The first one is an important fix that has to be applied as far
back as possible (hence CC'ing linux-stable).
- The second is more of an improvement. That's why it doesn't have the
Fixes tag.
I'd like to thank Si-Wei for the effort of finding and fixing these
issues. Especially the first issue which was very well hidden and
was there since day 1.
Si-Wei Liu (2):
vdpa/mlx5: Fix PA offset with unaligned starting iotlb map
vdpa/mlx5: Fix suboptimal range on iotlb iteration
drivers/vdpa/mlx5/core/mr.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
2.46.1
next reply other threads:[~2024-10-21 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 13:40 Dragos Tatulea [this message]
2024-10-21 13:40 ` [PATCH vhost 1/2] vdpa/mlx5: Fix PA offset with unaligned starting iotlb map Dragos Tatulea
2024-10-25 8:42 ` Jason Wang
2024-10-21 13:40 ` [PATCH vhost 2/2] vdpa/mlx5: Fix suboptimal range on iotlb iteration Dragos Tatulea
2024-10-25 8:42 ` Jason Wang
2024-11-13 6:32 ` Michael S. Tsirkin
2024-11-13 14:33 ` Dragos Tatulea
2024-11-13 14:49 ` Michael S. Tsirkin
2024-11-13 15:01 ` Dragos Tatulea
2024-11-13 15:06 ` Michael S. Tsirkin
2024-11-11 8:58 ` [PATCH vhost 0/2] vdpa/mlx5: Iova mapping related fixes Dragos Tatulea
2024-11-13 1:45 ` Jason Wang
2024-11-13 6:32 ` Michael S. Tsirkin
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=20241021134040.975221-1-dtatulea@nvidia.com \
--to=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gal@nvidia.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=si-wei.liu@oracle.com \
--cc=virtualization@lists.linux.dev \
--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.