mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Si-Wei Liu <si-wei.liu@oracle.com>
To: mst@redhat.com, jasowang@redhat.com, parav@nvidia.com, elic@nvidia.com
Cc: virtualization@lists.linux-foundation.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/6] features provisioning fixes and mlx5_vdpa support
Date: Mon, 6 Feb 2023 15:22:10 -0800	[thread overview]
Message-ID: <417def2e-dc9b-231f-bc49-52e4b8952c6b@oracle.com> (raw)
In-Reply-To: <1675724880-7216-1-git-send-email-si-wei.liu@oracle.com>

Apologies folks. Please ignore the patches posted with an incorrect 
"[PATCH v3 ...]" subject in this thread. I've resent the patch with 
subject line corrected:

Message-Id: 1675725124-7375-1-git-send-email-si-wei.liu@oracle.com

Sorry again,
-Siwei

On 2/6/2023 3:07 PM, 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/
>
> ---
> v3 -> v4:
>    - rewrite while loop to a for loop per mst's call
>    - fix wording in the subject of patch
> v2 -> v3:
>    - fix incorrect reference of local variable in future patch
>    - prohibit per-device bitmask macro from exposure in uapi header
>    - add fixes tag
> v1 -> v2:
>    - include specific attribute info to error message
>    - move conditional feature presence in mlx5_vdpa config space
>      to a separate patch
>    - remove redundant check
> ---
>
> 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
>    vdpa: validate device feature provisioning against supported class
>    vdpa/mlx5: make MTU/STATUS presence conditional on feature bits
>    vdpa/mlx5: support device features provisioning
>
>   drivers/vdpa/mlx5/net/mlx5_vnet.c |  71 ++++++++++++++++++++------
>   drivers/vdpa/vdpa.c               | 103 ++++++++++++++++++++++++++++++++------
>   2 files changed, 144 insertions(+), 30 deletions(-)
>


      parent reply	other threads:[~2023-02-06 23:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 23:07 Si-Wei Liu
2023-02-06 23:07 ` [PATCH v3 1/6] vdpa: fix improper error message when adding vdpa dev Si-Wei Liu
2023-02-06 23:07 ` [PATCH v3 2/6] vdpa: conditionally read STATUS in config space Si-Wei Liu
2023-02-06 23:07 ` [PATCH v3 3/6] vdpa: validate provisioned device features against specified attribute Si-Wei Liu
2023-02-06 23:07 ` [PATCH v3 4/6] vdpa: validate device feature provisioning against supported class Si-Wei Liu
2023-02-06 23:07 ` [PATCH v3 5/6] vdpa/mlx5: make MTU/STATUS presence conditional on feature bits Si-Wei Liu
2023-02-06 23:08 ` [PATCH v3 6/6] vdpa/mlx5: support device features provisioning Si-Wei Liu
2023-02-06 23:22 ` Si-Wei Liu [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=417def2e-dc9b-231f-bc49-52e4b8952c6b@oracle.com \
    --to=si-wei.liu@oracle.com \
    --cc=elic@nvidia.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.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

all inboxes | Powered by JetHome®