search for: vp_test_vendor_id

...his? >> >> Thanks > If virtio vendor id is used then standard driver is expected > to bind, right? Maybe use a dedicated vendor id? I meant something like: static const struct pci_device_id vp_vdpa_id_table[] = { ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, ??? { 0 } }; Thanks

...his? >> >> Thanks > If virtio vendor id is used then standard driver is expected > to bind, right? Maybe use a dedicated vendor id? I meant something like: static const struct pci_device_id vp_vdpa_id_table[] = { ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, ??? { 0 } }; Thanks

...used then standard driver is expected >>> to bind, right? Maybe use a dedicated vendor id? >> >> I meant something like: >> >> static const struct pci_device_id vp_vdpa_id_table[] = { >> ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, >> VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, >> ??? { 0 } >> }; >> >> Thanks >> > Then regular virtio will still bind to it. It has > > drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }, > > IFCVF use this to avoid the binding...

...used then standard driver is expected >>> to bind, right? Maybe use a dedicated vendor id? >> >> I meant something like: >> >> static const struct pci_device_id vp_vdpa_id_table[] = { >> ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, >> VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, >> ??? { 0 } >> }; >> >> Thanks >> > Then regular virtio will still bind to it. It has > > drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }, > > IFCVF use this to avoid the binding...

On 2020/6/2 ??3:08, Jason Wang wrote: >> >>> +static const struct pci_device_id vp_vdpa_id_table[] = { >>> +??? { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }, >>> +??? { 0 } >>> +}; >> This looks like it'll create a mess with either virtio pci >> or vdpa being loaded at random. Maybe just don't specify >> any IDs for

...virtio vendor id is used then standard driver is expected > > to bind, right? Maybe use a dedicated vendor id? > > > I meant something like: > > static const struct pci_device_id vp_vdpa_id_table[] = { > ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, > VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, > ??? { 0 } > }; > > Thanks > Then regular virtio will still bind to it. It has drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }, -- MST

...t; > > to bind, right? Maybe use a dedicated vendor id? > > > > > > I meant something like: > > > > > > static const struct pci_device_id vp_vdpa_id_table[] = { > > > ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, > > > VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, > > > ??? { 0 } > > > }; > > > > > > Thanks > > > > > Then regular virtio will still bind to it. It has > > > > drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }...

On 2020/6/2 ??3:08, Jason Wang wrote: >> >>> +static const struct pci_device_id vp_vdpa_id_table[] = { >>> +??? { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }, >>> +??? { 0 } >>> +}; >> This looks like it'll create a mess with either virtio pci >> or vdpa being loaded at random. Maybe just don't specify >> any IDs for

...t;>>>> to bind, right? Maybe use a dedicated vendor id? >>>> I meant something like: >>>> >>>> static const struct pci_device_id vp_vdpa_id_table[] = { >>>> ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, >>>> VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, >>>> ??? { 0 } >>>> }; >>>> >>>> Thanks >>>> >>> Then regular virtio will still bind to it. It has >>> >>> drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRAN...

...t;>>>> to bind, right? Maybe use a dedicated vendor id? >>>> I meant something like: >>>> >>>> static const struct pci_device_id vp_vdpa_id_table[] = { >>>> ??? { PCI_DEVICE_SUB(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID, >>>> VP_TEST_VENDOR_ID, VP_TEST_DEVICE_ID) }, >>>> ??? { 0 } >>>> }; >>>> >>>> Thanks >>>> >>> Then regular virtio will still bind to it. It has >>> >>> drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRAN...