virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Si-Wei Liu <si-wei.liu@oracle.com>
Cc: linux-kernel@vger.kernel.org, elic@nvidia.com,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/6] features provisioning fixes and mlx5_vdpa support
Date: Thu, 2 Feb 2023 12:30:45 -0500	[thread overview]
Message-ID: <20230202123024-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1675207327-22289-1-git-send-email-si-wei.liu@oracle.com>

On Tue, Jan 31, 2023 at 03:22:01PM -0800, Si-Wei Liu wrote:
> This patchset is pre-requisite to export and provision device
> config attributes and features for vdpa live migration, in a way
> backward and forward compatibility can be retained. The follow up
> work [1] will need to be built around the new feature provisioning
> uAPI, with which it's easier to formalize migration compatibility
> support at the driver level.
> 
> Thanks,
> -Siwei
> 
> [1] [PATCH v3 0/4] vDPA: initial config export via "vdpa dev show"
> https://lore.kernel.org/virtualization/1666392237-4042-1-git-send-email-si-wei.liu@oracle.com/

1-6 look like bugfixes right?

> ---
> 
> Si-Wei Liu (6):
>   vdpa: fix improper error message when adding vdpa dev
>   vdpa: conditionally read STATUS in config space
>   vdpa: validate provisioned device features against specified attribute
>   virtio: VIRTIO_DEVICE_F_MASK for all per-device features
>   vdpa: validate device feature provisioning against supported class
>   vdpa/mlx5: support device features provisioning
> 
>  drivers/vdpa/mlx5/net/mlx5_vnet.c  | 72 ++++++++++++++++++++++------
>  drivers/vdpa/vdpa.c                | 98 ++++++++++++++++++++++++++++++++------
>  include/uapi/linux/virtio_config.h |  8 ++++
>  3 files changed, 149 insertions(+), 29 deletions(-)
> 
> -- 
> 1.8.3.1

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2023-02-02 17:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 23:22 [PATCH 0/6] features provisioning fixes and mlx5_vdpa support Si-Wei Liu
2023-01-31 23:22 ` [PATCH 1/6] vdpa: fix improper error message when adding vdpa dev Si-Wei Liu
2023-01-31 23:22 ` [PATCH 2/6] vdpa: conditionally read STATUS in config space Si-Wei Liu
2023-01-31 23:22 ` [PATCH 3/6] vdpa: validate provisioned device features against specified attribute Si-Wei Liu
2023-01-31 23:22 ` [PATCH 4/6] virtio: VIRTIO_DEVICE_F_MASK for all per-device features Si-Wei Liu
2023-01-31 23:22 ` [PATCH 5/6] vdpa: validate device feature provisioning against supported class Si-Wei Liu
2023-01-31 23:22 ` [PATCH 6/6] vdpa/mlx5: support device features provisioning Si-Wei Liu
2023-01-31 23:25 ` [PATCH 0/6] features provisioning fixes and mlx5_vdpa support Si-Wei Liu
2023-02-02 17:30 ` Michael S. Tsirkin [this message]
2023-02-02 22:07   ` Si-Wei Liu
  -- strict thread matches above, loose matches on Subject: below --
2023-01-30 20:30 Si-Wei Liu

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=20230202123024-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=elic@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si-wei.liu@oracle.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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).