mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "Michael S . Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Eugenio Perez Martin <eperezma@redhat.com>,
	Si-Wei Liu <si-wei.liu@oracle.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	virtualization@lists.linux-foundation.org,
	Dragos Tatulea <dtatulea@nvidia.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gal Pressman <galp@nvidia.com>, Parav Pandit <parav@nvidia.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: (subset) [PATCH vhost 0/7] vdpa/mlx5: Add support for resumable vqs
Date: Mon, 04 Dec 2023 15:10:37 +0200	[thread overview]
Message-ID: <170169543706.44375.3181832396401755311.b4-ty@kernel.org> (raw)
In-Reply-To: <20231201104857.665737-1-dtatulea@nvidia.com>


On Fri, 01 Dec 2023 12:48:50 +0200, Dragos Tatulea wrote:
> Add support for resumable vqs in the driver. This is a firmware feature
> that can be used for the following benefits:
> - Full device .suspend/.resume.
> - .set_map doesn't need to destroy and create new vqs anymore just to
>   update the map. When resumable vqs are supported it is enough to
>   suspend the vqs, set the new maps, and then resume the vqs.
> 
> [...]

Applied, thanks!

[1/7] vdpa/mlx5: Expose resumable vq capability
      https://git.kernel.org/rdma/rdma/c/b24910e1be0e76

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>

      parent reply	other threads:[~2023-12-04 13:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 10:48 Dragos Tatulea
2023-12-01 10:48 ` [PATCH mlx5-vhost 1/7] vdpa/mlx5: Expose resumable vq capability Dragos Tatulea
2023-12-01 10:48 ` [PATCH vhost 2/7] vdpa/mlx5: Split function into locked and unlocked variants Dragos Tatulea
2023-12-01 11:46   ` Eugenio Perez Martin
2023-12-01 10:48 ` [PATCH vhost 3/7] vdpa/mlx5: Allow modifying multiple vq fields in one modify command Dragos Tatulea
2023-12-01 14:47   ` Eugenio Perez Martin
2023-12-01 15:26     ` Dragos Tatulea
2023-12-01 10:48 ` [PATCH vhost 4/7] vdpa/mlx5: Introduce per vq and device resume Dragos Tatulea
2023-12-01 14:51   ` Eugenio Perez Martin
2023-12-01 10:48 ` [PATCH vhost 5/7] vdpa/mlx5: Mark vq addrs for modification in hw vq Dragos Tatulea
2023-12-01 10:48 ` [PATCH vhost 6/7] vdpa/mlx5: Mark vq state " Dragos Tatulea
2023-12-01 15:18   ` Eugenio Perez Martin
2023-12-01 10:48 ` [PATCH vhost 7/7] vdpa/mlx5: Use vq suspend/resume during .set_map Dragos Tatulea
2023-12-02 20:26 ` [PATCH vhost 0/7] vdpa/mlx5: Add support for resumable vqs Michael S. Tsirkin
2023-12-03 15:21   ` Dragos Tatulea
2023-12-03 16:23     ` Michael S. Tsirkin
2023-12-04  8:53       ` Dragos Tatulea
2023-12-04  8:55         ` Michael S. Tsirkin
2023-12-04  9:16           ` Dragos Tatulea
2023-12-04 11:04             ` Michael S. Tsirkin
2023-12-04 11:18               ` Dragos Tatulea
2023-12-04 13:10 ` Leon Romanovsky [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=170169543706.44375.3181832396401755311.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=dtatulea@nvidia.com \
    --cc=eperezma@redhat.com \
    --cc=galp@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=saeedm@nvidia.com \
    --cc=si-wei.liu@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®