linux-kernel - Re: [PATCH 0/6] features provisioning fixes and mlx5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2119e210-a272-6ef9-c364-8c8cd9f28d5e@oracle.com>
Date:   Tue, 31 Jan 2023 15:25:43 -0800
From:   Si-Wei Liu <si-wei.liu@...cle.com>
To:     mst@...hat.com, jasowang@...hat.com, parav@...dia.com,
        elic@...dia.com
Cc:     linux-kernel@...r.kernel.org,
        virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH 0/6] features provisioning fixes and mlx5_vdpa support

Please disregard this series for v1, please refer to the v2 at:

Message-ID: 1675207345-22328-1-git-send-email-si-wei.liu@...cle.com

Apologies I accidentally got v1 resent at the same time when v2 was sent.

-Siwei

On 1/31/2023 3:22 PM, Si-Wei Liu wrote:
> You are currently receiving this informational message with the original email attached. We need your help in notifying the team or sender responsible for this mail flow to ensure future email is delivered properly.
>
> The host that sent this message is not compliant with Oracle's email security policy (DMARC). Please notify the person(s) responsible for this message and share the content below so they can take actions to resolve their issue.
>
> If you have no idea who is responsible, then please address the #ww-oracle-dmarc slack channel for assistance.
>
> Deadlines
> 	• We plan to move to quarantine non-compliant messages early 2023 (date to be determined).  After this date, if the issues are not fixed, messages will be held in a folder on our email gateway and will not be delivered to you.
> 	• We will then move to reject early 2023 (date to be determined).  After this date, messages will be rejected.
>
> For more technical resources and information, see:
> https://confluence.oci.oraclecorp.com/display/EMAIL/DMARC+for+Oracle+IT+and+Email+Delivery+Frequently+Asked+Questions
> https://confluence.oraclecorp.com/confluence/display/OITGLOBAL/DMARC+Global+FAQ
>
> Thank you in advance for your attention to this matter.
>
> ----------------------------------------------------------------------
> 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/
>
> ---
>
> 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(-)
>