Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp4849247iob; Mon, 9 May 2022 03:08:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyzVf7+fcXqAela4qLjHdW32DKqCP8hTci5QmkJ8bX+2IVNZZO2cBsYOTKPtJsPEJyxURey X-Received: by 2002:a17:90b:17d0:b0:1dc:ddce:9c25 with SMTP id me16-20020a17090b17d000b001dcddce9c25mr15863266pjb.232.1652090898183; Mon, 09 May 2022 03:08:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652090898; cv=none; d=google.com; s=arc-20160816; b=i4Jx01C1DQ2z1aX1kLgepC0MG9nv0cxC9856rnh7/jK4png+oz2hK8rLqEAI69RarI J53bbpo6cq4npxcD0GLOL4xt31tjzymwJsnknyGbNxhz859khfK2ysgBcSRiZDeAx4I9 Hjc4ozFCnfs9XBY1JDEVjh0rr7zvltS8tzpcRfWP51nzGLd11bGueNRc7/8M5gixlIrG Vz0Ct3cuTjq3RzNWH4EELh2j22DOhdOcPGeqJe9RAQy9wdCeoFomqMH65tjEMde2EZOE Iv0ybb26NaGIPCy/VuS8W0/IWsrrP8J5q0wxy4WDCU6vh002YCZEAv3CdBc1sojpPL3u tQsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=G97dy4AVAE1GL5QBc/XNOK50cRVojaBVv4PlJyXXKIE=; b=DvmuSL1SPsh12B24mH3ICZO1mty+M5arJVqbFe1OeiUPL55r7CLezP34aygPUFZEKU u8Za0nVwgT473KVhVWQa6e351cZ2/XP2WkRDRO7PGOUbFhamzkkdBy67SGHHMJ03O/PV rKMk400J9ln42+wCJfWNkD4ZV13HhXx9Fv4KL4QCi6dBDB1KQCipVnUEkpOP8aKZhKOB ZJHIBRPD/jqKnVGElWOo6GeLZLPUxT/Z0gwSxCjPMfjzSq2pONSgZNNezP3qipoaAQNc gIs2Rc26Kw/R77Rdbgp3lqaf/2rE7cQGeWhYCh0h0eV2KVEe1tvj1zER7CFodBj+45vx 5nfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=C8tCso7q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id c18-20020a170902c2d200b0015cd18f032fsi9761724pla.155.2022.05.09.03.08.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 May 2022 03:08:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=C8tCso7q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 0D77F248DD; Mon, 9 May 2022 02:47:38 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233955AbiEIDw3 (ORCPT + 99 others); Sun, 8 May 2022 23:52:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54716 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232231AbiEIDqT (ORCPT ); Sun, 8 May 2022 23:46:19 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D0F903FBD8 for ; Sun, 8 May 2022 20:42:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1652067745; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=G97dy4AVAE1GL5QBc/XNOK50cRVojaBVv4PlJyXXKIE=; b=C8tCso7qqvP3vdGKW4ao0jRE3uWquKjv8iTiVxsiLwF7jEd9qj0YgsIUjjaU4RhuDUsbJz 9ZGu6UgqiDG4Pz3qijvgViFpxw8REg8a/SUp/u4gmtJ+/W6Z350qO+HH5WL3x9RwBeFzo9 eGagBYrbKligZpN9ZicXbkSXxtDipyY= Received: from mail-lj1-f198.google.com (mail-lj1-f198.google.com [209.85.208.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-640-KdnyKlaEPmWMAj4bckte9Q-1; Sun, 08 May 2022 23:42:23 -0400 X-MC-Unique: KdnyKlaEPmWMAj4bckte9Q-1 Received: by mail-lj1-f198.google.com with SMTP id q7-20020a2e8747000000b0024f2d363986so3728928ljj.5 for ; Sun, 08 May 2022 20:42:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=G97dy4AVAE1GL5QBc/XNOK50cRVojaBVv4PlJyXXKIE=; b=r5XNtWLEtaCkhaPf2ULLUJo88T9oCtCPQX6FngRJN+slGDRJ7F/tMVPUbnH/SUSQd8 429OxQw132VLaTMqtKLJkhuTuS9oA/2lilNC/YXGxBDuv/jkBc3Ol0K84w0uz7vu3wdI McFxwQKUVMC6EOHaA1uGTsPqAjraMU7cySmb2eHOCtoP2r7mXAs8r6b3rqTELWHZI5TI qAS2ML7Cd7XxTGSp9EKgSYxGX+HLlEGr49/Oe3B7cyj7qpMVgdF/kFBAWHekHWPyfVxi ANjeH/kOwbxwaZXm5Mi9FZMLOMMScuYCgWThy/tgXwLPgPYFcPlypDvasg7cSrMYgJ/W wN8Q== X-Gm-Message-State: AOAM531z+SvRQMH9EHrmWb0GQWwDttzU1kwccGlXIOehztzQyV1nfsi8 A+nu8rHCr1gFNTJmrAIHavMN5/S76IT/uOEu86dOZnfyFj7+BJYA50BvgJOyHOg3K88WSxzrG29 VEVFONDexzbyd63cTXZpVhynXqV9/pdZ1VCldETFx X-Received: by 2002:a05:651c:89:b0:250:87c9:d4e6 with SMTP id 9-20020a05651c008900b0025087c9d4e6mr9454722ljq.315.1652067741662; Sun, 08 May 2022 20:42:21 -0700 (PDT) X-Received: by 2002:a05:651c:89:b0:250:87c9:d4e6 with SMTP id 9-20020a05651c008900b0025087c9d4e6mr9454689ljq.315.1652067741377; Sun, 08 May 2022 20:42:21 -0700 (PDT) MIME-Version: 1.0 References: <20220330180436.24644-1-gdawar@xilinx.com> In-Reply-To: <20220330180436.24644-1-gdawar@xilinx.com> From: Jason Wang Date: Mon, 9 May 2022 11:42:10 +0800 Message-ID: Subject: Re: [PATCH v2 00/19] Control VQ support in vDPA To: "Michael S. Tsirkin" Cc: kvm , Gautam Dawar , virtualization , netdev , linux-kernel , Martin Petrus Hubertus Habets , Harpreet Singh Anand , Martin Porter , Pablo Cascon Katchadourian , Dinan Gunawardena , tanuj.kamde@amd.com, habetsm.xilinx@gmail.com, ecree.xilinx@gmail.com, eperezma , Gautam Dawar , Wu Zongyong , Christophe JAILLET , Eli Cohen , Zhu Lingshan , Stefano Garzarella , Xie Yongji , Si-Wei Liu , Parav Pandit , Longpeng , Dan Carpenter , Zhang Min Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 31, 2022 at 2:05 AM Gautam Dawar wrote: > > Hi All: > > This series tries to add the support for control virtqueue in vDPA. > > Control virtqueue is used by networking device for accepting various > commands from the driver. It's a must to support multiqueue and other > configurations. > > When used by vhost-vDPA bus driver for VM, the control virtqueue > should be shadowed via userspace VMM (Qemu) instead of being assigned > directly to Guest. This is because Qemu needs to know the device state > in order to start and stop device correctly (e.g for Live Migration). > > This requies to isolate the memory mapping for control virtqueue > presented by vhost-vDPA to prevent guest from accessing it directly. > > To achieve this, vDPA introduce two new abstractions: > > - address space: identified through address space id (ASID) and a set > of memory mapping in maintained > - virtqueue group: the minimal set of virtqueues that must share an > address space > > Device needs to advertise the following attributes to vDPA: > > - the number of address spaces supported in the device > - the number of virtqueue groups supported in the device > - the mappings from a specific virtqueue to its virtqueue groups > > The mappings from virtqueue to virtqueue groups is fixed and defined > by vDPA device driver. E.g: > > - For the device that has hardware ASID support, it can simply > advertise a per virtqueue group. > - For the device that does not have hardware ASID support, it can > simply advertise a single virtqueue group that contains all > virtqueues. Or if it wants a software emulated control virtqueue, it > can advertise two virtqueue groups, one is for cvq, another is for > the rest virtqueues. > > vDPA also allow to change the association between virtqueue group and > address space. So in the case of control virtqueue, userspace > VMM(Qemu) may use a dedicated address space for the control virtqueue > group to isolate the memory mapping. > > The vhost/vhost-vDPA is also extend for the userspace to: > > - query the number of virtqueue groups and address spaces supported by > the device > - query the virtqueue group for a specific virtqueue > - assocaite a virtqueue group with an address space > - send ASID based IOTLB commands > > This will help userspace VMM(Qemu) to detect whether the control vq > could be supported and isolate memory mappings of control virtqueue > from the others. > > To demonstrate the usage, vDPA simulator is extended to support > setting MAC address via a emulated control virtqueue. > > Please review. Michael, this looks good to me, do you have comments on this? Thanks > > Changes since RFC v2: > > - Fixed memory leak for asid 0 in vhost_vdpa_remove_as() > - Removed unnecessary NULL check for iotlb in vhost_vdpa_unmap() and > changed its return type to void. > - Removed insignificant used_as member field from struct vhost_vdpa. > - Corrected the iommu parameter in call to vringh_set_iotlb() from > vdpasim_set_group_asid() > - Fixed build errors with vdpa_sim_net > - Updated alibaba, vdpa_user and virtio_pci vdpa parent drivers to > call updated vDPA APIs and ensured successful build > - Tested control (MAC address configuration) and data-path using > single virtqueue pair on Xilinx (now AMD) SN1022 SmartNIC device > and vdpa_sim_net software device using QEMU release at [1] > - Removed two extra blank lines after set_group_asid() in > include/linux/vdpa.h > > Changes since v1: > > - Rebased the v1 patch series on vhost branch of MST vhost git repo > git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/log/?h=vhost > - Updates to accommodate vdpa_sim changes from monolithic module in > kernel used v1 patch series to current modularized class (net, block) > based approach. > - Added new attributes (ngroups and nas) to "vdpasim_dev_attr" and > propagated them from vdpa_sim_net to vdpa_sim > - Widened the data-type for "asid" member of vhost_msg_v2 to __u32 > to accommodate PASID > - Fixed the buildbot warnings > - Resolved all checkpatch.pl errors and warnings > - Tested both control and datapath with Xilinx Smartnic SN1000 series > device using QEMU implementing the Shadow virtqueue and support for > VQ groups and ASID available at [1] > > Changes since RFC: > > - tweak vhost uAPI documentation > - switch to use device specific IOTLB really in patch 4 > - tweak the commit log > - fix that ASID in vhost is claimed to be 32 actually but 16bit > actually > - fix use after free when using ASID with IOTLB batching requests > - switch to use Stefano's patch for having separated iov > - remove unused "used_as" variable > - fix the iotlb/asid checking in vhost_vdpa_unmap() > > [1] Development QEMU release with support for SVQ, VQ groups and ASID: > github.com/eugpermar/qemu/releases/tag/vdpa_sw_live_migration.d%2F > asid_groups-v1.d%2F00 > > Thanks > > Gautam Dawar (19): > vhost: move the backend feature bits to vhost_types.h > virtio-vdpa: don't set callback if virtio doesn't need it > vhost-vdpa: passing iotlb to IOMMU mapping helpers > vhost-vdpa: switch to use vhost-vdpa specific IOTLB > vdpa: introduce virtqueue groups > vdpa: multiple address spaces support > vdpa: introduce config operations for associating ASID to a virtqueue > group > vhost_iotlb: split out IOTLB initialization > vhost: support ASID in IOTLB API > vhost-vdpa: introduce asid based IOTLB > vhost-vdpa: introduce uAPI to get the number of virtqueue groups > vhost-vdpa: introduce uAPI to get the number of address spaces > vhost-vdpa: uAPI to get virtqueue group id > vhost-vdpa: introduce uAPI to set group ASID > vhost-vdpa: support ASID based IOTLB API > vdpa_sim: advertise VIRTIO_NET_F_MTU > vdpa_sim: factor out buffer completion logic > vdpa_sim: filter destination mac address > vdpasim: control virtqueue support > > drivers/vdpa/alibaba/eni_vdpa.c | 2 +- > drivers/vdpa/ifcvf/ifcvf_main.c | 8 +- > drivers/vdpa/mlx5/net/mlx5_vnet.c | 11 +- > drivers/vdpa/vdpa.c | 5 + > drivers/vdpa/vdpa_sim/vdpa_sim.c | 100 ++++++++-- > drivers/vdpa/vdpa_sim/vdpa_sim.h | 3 + > drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 169 +++++++++++++---- > drivers/vdpa/vdpa_user/vduse_dev.c | 3 +- > drivers/vdpa/virtio_pci/vp_vdpa.c | 2 +- > drivers/vhost/iotlb.c | 23 ++- > drivers/vhost/vdpa.c | 267 +++++++++++++++++++++------ > drivers/vhost/vhost.c | 23 ++- > drivers/vhost/vhost.h | 4 +- > drivers/virtio/virtio_vdpa.c | 2 +- > include/linux/vdpa.h | 44 ++++- > include/linux/vhost_iotlb.h | 2 + > include/uapi/linux/vhost.h | 26 ++- > include/uapi/linux/vhost_types.h | 11 +- > 18 files changed, 563 insertions(+), 142 deletions(-) > > -- > 2.30.1 >