From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 24E10C35249 for ; Wed, 5 Feb 2020 07:58:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F2D57217BA for ; Wed, 5 Feb 2020 07:58:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728062AbgBEH6C convert rfc822-to-8bit (ORCPT ); Wed, 5 Feb 2020 02:58:02 -0500 Received: from mga09.intel.com ([134.134.136.24]:42374 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725497AbgBEH6C (ORCPT ); Wed, 5 Feb 2020 02:58:02 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Feb 2020 23:58:00 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,405,1574150400"; d="scan'208";a="264134381" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga002.fm.intel.com with ESMTP; 04 Feb 2020 23:58:00 -0800 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 4 Feb 2020 23:57:59 -0800 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 4 Feb 2020 23:57:38 -0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.5]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.222]) with mapi id 14.03.0439.000; Wed, 5 Feb 2020 15:57:36 +0800 From: "Liu, Yi L" To: Alex Williamson , "kvm@vger.kernel.org" CC: "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "dev@dpdk.org" , "mtosatti@redhat.com" , "thomas@monjalon.net" , "bluca@debian.org" , "jerinjacobk@gmail.com" , "Richardson, Bruce" , "cohuck@redhat.com" Subject: RE: [RFC PATCH 0/7] vfio/pci: SR-IOV support Thread-Topic: [RFC PATCH 0/7] vfio/pci: SR-IOV support Thread-Index: AQHV26+tAcTUgIsbdUG5kuoMQU0tFqgLJReAgAESvVA= Date: Wed, 5 Feb 2020 07:57:36 +0000 Message-ID: References: <158085337582.9445.17682266437583505502.stgit@gimli.home> <20200204161737.34696b91@w520.home> In-Reply-To: <20200204161737.34696b91@w520.home> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZWJkYjRjOWQtNDUxYi00MDk1LWEwNGEtOTJlZDY2MjE4Nzc2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiRHl3WlJ2bzBQR0lFa2ErVVZjZWFHYlpGN2xPNlwvelU0ZjFxVUtvamZQdzR3bVFIUXBEUzlvbm1UcVwvRU5sZmQ5In0= x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org > From: Alex Williamson > Sent: Wednesday, February 5, 2020 7:18 AM > To: kvm@vger.kernel.org > Subject: Re: [RFC PATCH 0/7] vfio/pci: SR-IOV support > > > Promised example QEMU test case... > > commit 3557c63bcb286c71f3f7242cad632edd9e297d26 > Author: Alex Williamson > Date: Tue Feb 4 13:47:41 2020 -0700 > > vfio-pci: QEMU support for vfio-pci VF tokens > > Example support for using a vf_token to gain access to a device as > well as using the VFIO_DEVICE_FEATURE interface to set the VF token. > Note that the kernel will disregard the additional option where it's > not required, such as opening the PF with no VF users, so we can > always provide it. > > NB. It's unclear whether there's value to this QEMU support without > further exposure of SR-IOV within a VM. This is meant mostly as a > test case where the real initial users will likely be DPDK drivers. > > Signed-off-by: Alex Williamson Just curious how UUID is used across the test. Should the QEMU which opens VFs add the vfio_token=UUID or the QEMU which opens PF add the vfio_token=UUID? or both should add vfio_token=UUID. Regards, Yi Liu