Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp4253429ybg; Mon, 8 Jun 2020 03:10:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwy8S0PPInAfyCFDHXraEkEXw1P9Cig3/5wyJBpiJioSAVj3Zt2sSC4IWXacARUfolPhX1D X-Received: by 2002:a50:fb01:: with SMTP id d1mr21241712edq.94.1591611045943; Mon, 08 Jun 2020 03:10:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591611045; cv=none; d=google.com; s=arc-20160816; b=deScSjK47mBFP3FAzYy9iU7+zK7onDI/T0MZ8RcafhiXioSmwcuzEkwkPzTP6280nt 3FqpQZkxGUFWAsu/sPrPju0NM2FicZE6XMDGW2ijQ4wTxeW4aZkSig8d0a5TchItlQEk DP2OCp2JGRnbHbAHVTJ8KocwSkw5g6IuPrVHngXhPJH/ehTtIDGPgXDpTyL2ffHSyXf9 9O3k2anMSz9MCYv83KdsPGhn3K/TCgQcwNgkawGJdbiwrHanA4rzenP1+4YQBoeuzXzz YKTI4qz0a7NKHy407mnJu+tVCV2e3AWWY7JopsKxkChqqLFNdZulrICagoP6g1BlclEQ 5XoQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=J8KdBsIeUG7CqXgAwlXgq2ronkJRHUa9z02ZSl84hDE=; b=uoGj3rMlciAB5f184LVqsxx3cf2JbA09Ex12LQHdSLhkmlKPWZIf/DPBdMdR7Sl91H vEiwwykZu/8X4eoxUN3yabknktIXU3nLhyI4/dAvIyv8BbIa4WPUAu+YQl9LOe2bVwLq zmOMCuWWBd9XhwhtbZ7+tJzztBdFQpn9q0oBCyk3VtdbOvJiC3Uy/J1va9Fd/8zr54bS l9Co3mAdOVTfErKRVf3opKFNH87ZMWf4lrNweVnEFhbSQPKBYY8EotZvRe59O6LZBYZ7 BYmSCupHkiaPkeD7uaxFEPf1BTBvhd/KJxhw0xl0K9CZLdLePUTaI5fNw3vOzWaO+LYz 5/Ag== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=H3NGIDBP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.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 vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c10si8567554edj.163.2020.06.08.03.10.22; Mon, 08 Jun 2020 03:10:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=H3NGIDBP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.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: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729370AbgFHKIF (ORCPT + 99 others); Mon, 8 Jun 2020 06:08:05 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:42480 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729356AbgFHKIE (ORCPT ); Mon, 8 Jun 2020 06:08:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1591610883; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=J8KdBsIeUG7CqXgAwlXgq2ronkJRHUa9z02ZSl84hDE=; b=H3NGIDBPoAQe+Aa4VT1C4SgYx3BZfIuT/2hRfb+Ihu8kQRt7U5UODbrQsZgTI58n4TXeyX EhYYWpx3EQ8Q+gkYydPc/PtjFnyopvoZjbb/ePVC6r8I2pKSA00NV4/e6q6QiP3OEEI6pP DTP05RvkryoTUNt0nhi1VP3+g9Ycdhc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-165-RuHe18uhO4ac4yGJwcfsCw-1; Mon, 08 Jun 2020 06:07:58 -0400 X-MC-Unique: RuHe18uhO4ac4yGJwcfsCw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C584D8018AD; Mon, 8 Jun 2020 10:07:56 +0000 (UTC) Received: from [10.72.13.71] (ovpn-13-71.pek2.redhat.com [10.72.13.71]) by smtp.corp.redhat.com (Postfix) with ESMTP id C69136FF1B; Mon, 8 Jun 2020 10:07:40 +0000 (UTC) Subject: Re: [PATCH 5/6] vdpa: introduce virtio pci driver To: "Michael S. Tsirkin" Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, rob.miller@broadcom.com, lingshan.zhu@intel.com, eperezma@redhat.com, lulu@redhat.com, shahafs@mellanox.com, hanand@xilinx.com, mhabets@solarflare.com, gdawar@xilinx.com, saugatm@xilinx.com, vmireyno@marvell.com, zhangweining@ruijie.com.cn, eli@mellanox.com References: <5dbb0386-beeb-5bf4-d12e-fb5427486bb8@redhat.com> <6b1d1ef3-d65e-08c2-5b65-32969bb5ecbc@redhat.com> <20200607095012-mutt-send-email-mst@kernel.org> <9b1abd2b-232c-aa0f-d8bb-03e65fd47de2@redhat.com> <20200608021438-mutt-send-email-mst@kernel.org> <20200608052041-mutt-send-email-mst@kernel.org> <9d2571b6-0b95-53b3-6989-b4d801eeb623@redhat.com> <20200608054453-mutt-send-email-mst@kernel.org> <20200608055331-mutt-send-email-mst@kernel.org> From: Jason Wang Message-ID: <61117e6a-2568-d0f4-8713-d831af32814d@redhat.com> Date: Mon, 8 Jun 2020 18:07:36 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200608055331-mutt-send-email-mst@kernel.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/6/8 下午5:54, Michael S. Tsirkin wrote: > On Mon, Jun 08, 2020 at 05:46:52PM +0800, Jason Wang wrote: >> On 2020/6/8 下午5:45, Michael S. Tsirkin wrote: >>> On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: >>>>>> Looking at >>>>>> pci_match_one_device() it checks both subvendor and subdevice there. >>>>>> >>>>>> Thanks >>>>> But IIUC there is no guarantee that driver with a specific subvendor >>>>> matches in presence of a generic one. >>>>> So either IFC or virtio pci can win, whichever binds first. >>>> I'm not sure I get there. But I try manually bind IFCVF to qemu's >>>> virtio-net-pci, and it fails. >>>> >>>> Thanks >>> Right but the reverse can happen: virtio-net can bind to IFCVF first. >> >> That's kind of expected. The PF is expected to be bound to virtio-pci to >> create VF via sysfs. >> >> Thanks >> >> >> > Once VFs are created, don't we want IFCVF to bind rather than > virtio-pci? Yes, but for PF we need virtio-pci. Thanks >