From: Jason Wang <jasowang@redhat.com>
To: Rob Miller <rob.miller@broadcom.com>
Cc: Eugenio Perez Martin <eperezma@redhat.com>,
Virtio-Dev <virtio-dev@lists.oasis-open.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Michael Tsirkin <mst@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [virtio-dev] Dirty Page Tracking (DPT)
Date: Wed, 8 Apr 2020 06:00:51 -0400 (EDT) [thread overview]
Message-ID: <123421885.21147407.1586340051693.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAJPjb1KijQN39gC=8_hzBrt9zo0aX2uFAdPA7ynkmUv2bMFtEA@mail.gmail.com>
----- 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
next prev parent reply other threads:[~2020-04-08 10:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 15:40 [virtio-dev] Dirty Page Tracking (DPT) Rob Miller
2020-03-09 7:38 ` Michael S. Tsirkin
2020-03-09 8:50 ` Jason Wang
2020-03-09 10:13 ` Michael S. Tsirkin
2020-03-10 3:22 ` Jason Wang
2020-03-10 6:24 ` Michael S. Tsirkin
2020-03-10 6:39 ` Jason Wang
2020-03-18 15:13 ` Rob Miller
2020-03-19 3:35 ` Jason Wang
2020-03-19 11:17 ` Paolo Bonzini
2020-04-07 9:52 ` Eugenio Perez Martin
2020-04-07 10:27 ` Rob Miller
2020-04-07 16:31 ` Eugenio Perez Martin
2020-04-08 10:10 ` Jason Wang
2020-04-07 10:40 ` Rob Miller
2020-04-08 10:00 ` Jason Wang [this message]
2020-04-09 21:06 ` Michael S. Tsirkin
2020-04-10 2:40 ` Jason Wang
2020-04-13 12:15 ` Eugenio Perez Martin
2020-04-13 13:30 ` Rob Miller
2020-04-13 13:49 ` Jason Wang
2020-04-13 13:49 ` Jason Wang
2020-04-13 13:55 ` Jason Wang
2020-04-16 10:55 ` Eugenio Perez Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=123421885.21147407.1586340051693.JavaMail.zimbra@redhat.com \
--to=jasowang@redhat.com \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=quintela@redhat.com \
--cc=rob.miller@broadcom.com \
--cc=virtio-dev@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.