From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-7020-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 7F49C985EF2 for ; Wed, 8 Apr 2020 10:01:10 +0000 (UTC) Date: Wed, 8 Apr 2020 06:00:51 -0400 (EDT) From: Jason Wang Message-ID: <123421885.21147407.1586340051693.JavaMail.zimbra@redhat.com> In-Reply-To: References: <20200310021729-mutt-send-email-mst@kernel.org> <89358cf3-7ce0-7b60-f4a7-2672970a635e@redhat.com> <0f43a280-5425-3a10-1312-22ea87d320ca@redhat.com> MIME-Version: 1.0 Subject: Re: [virtio-dev] Dirty Page Tracking (DPT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: Rob Miller Cc: Eugenio Perez Martin , Virtio-Dev , Paolo Bonzini , Michael Tsirkin , Juan Quintela List-ID: ----- Original Message ----- > another question on vDPA vs vendor specific driver portion... > > Are the subsystem vendor & device IDs to be different from the primary (Red > Hat) versions as there has to be a way for a vendor specific driver to > "see" its device. Yes, any kinds of (PCI)device could be registered to the vDPA bus. For PCI driver, it supports exact mathing based on subsystem ID. E.g in IFCVF driver it does: static struct pci_device_id ifcvf_pci_ids[] = { { PCI_DEVICE_SUB(IFCVF_VENDOR_ID, IFCVF_DEVICE_ID, IFCVF_SUBSYS_VENDOR_ID, IFCVF_SUBSYS_DEVICE_ID) }, { 0 }, }; Which uses Redhat primary vendor ID but their own sybsysm vendor/device ID. Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org