Displaying 9 results from an estimated 9 matches for "ifcvf_subsys_vendor_id".
2020 Apr 09
2
[PATCH] vdpa: allow a 32 bit vq alignment
...tions(-)
diff --git a/drivers/vdpa/ifcvf/ifcvf_main.c b/drivers/vdpa/ifcvf/ifcvf_main.c
index 28d9e5de5675..abf6a061cab6 100644
--- a/drivers/vdpa/ifcvf/ifcvf_main.c
+++ b/drivers/vdpa/ifcvf/ifcvf_main.c
@@ -226,7 +226,7 @@ static u32 ifcvf_vdpa_get_vendor_id(struct vdpa_device *vdpa_dev)
return IFCVF_SUBSYS_VENDOR_ID;
}
-static u16 ifcvf_vdpa_get_vq_align(struct vdpa_device *vdpa_dev)
+static u32 ifcvf_vdpa_get_vq_align(struct vdpa_device *vdpa_dev)
{
return IFCVF_QUEUE_ALIGNMENT;
}
diff --git a/drivers/vdpa/vdpa_sim/vdpa_sim.c b/drivers/vdpa/vdpa_sim/vdpa_sim.c
index 72863d01a12a..7957d2d41fc4 100644
--...
2019 Nov 08
0
[PATCH 1/2] IFC hardware operation layer
...>
> +#include <linux/pci_regs.h>
> +#include <uapi/linux/virtio_net.h>
> +#include <uapi/linux/virtio_config.h>
> +#include <uapi/linux/virtio_pci.h>
> +
> +#define IFCVF_VENDOR_ID 0x1AF4
> +#define IFCVF_DEVICE_ID 0x1041
> +#define IFCVF_SUBSYS_VENDOR_ID 0x8086
> +#define IFCVF_SUBSYS_DEVICE_ID 0x001A
> +
> +#define IFCVF_MDEV_LIMIT 1
> +
> +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */...
2019 Nov 05
1
[PATCH 1/2] IFC hardware operation layer
...>
> +#include <linux/pci_regs.h>
> +#include <uapi/linux/virtio_net.h>
> +#include <uapi/linux/virtio_config.h>
> +#include <uapi/linux/virtio_pci.h>
> +
> +#define IFCVF_VENDOR_ID 0x1AF4
> +#define IFCVF_DEVICE_ID 0x1041
> +#define IFCVF_SUBSYS_VENDOR_ID 0x8086
> +#define IFCVF_SUBSYS_DEVICE_ID 0x001A
> +
> +#define IFCVF_MDEV_LIMIT 1
> +
> +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */...
2019 Nov 05
0
[PATCH 1/2] IFC hardware operation layer
...nux/virtio_config.h>
> +#include <uapi/linux/virtio_pci.h>
> +
> +#define IFCVF_VENDOR_ID 0x1AF4
> +#define IFCVF_DEVICE_ID 0x1041
I am confused by the above.
They are used by the virtio layer right?
So why isn't the id VIRTIO_ID_NET then?
> +#define IFCVF_SUBSYS_VENDOR_ID 0x8086
> +#define IFCVF_SUBSYS_DEVICE_ID 0x001A
> +
> +#define IFCVF_MDEV_LIMIT 1
> +
> +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */...
2019 Oct 16
0
[RFC 2/2] vhost: IFC VF vdpa layer
...apter(adapter);
> + pci_free_irq_vectors(pdev);
> +
> + pci_release_regions(pdev);
> + pci_disable_device(pdev);
> +
> + kfree(adapter);
> +}
> +
> +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 },
> +};
> +MODULE_DEVICE_TABLE(pci, ifcvf_pci_ids);
> +
> +static struct pci_driver ifcvf_driver = {
> + .name = IFCVF_DRIVER_NAME,
> + .id_table = ifcvf_pci_ids,
> + .probe = ifcvf_probe,
> + .remove = ifcvf_remove,...
2019 Nov 06
0
[PATCH 1/2] IFC hardware operation layer
...>
> +#include <linux/pci_regs.h>
> +#include <uapi/linux/virtio_net.h>
> +#include <uapi/linux/virtio_config.h>
> +#include <uapi/linux/virtio_pci.h>
> +
> +#define IFCVF_VENDOR_ID 0x1AF4
> +#define IFCVF_DEVICE_ID 0x1041
> +#define IFCVF_SUBSYS_VENDOR_ID 0x8086
> +#define IFCVF_SUBSYS_DEVICE_ID 0x001A
> +
> +#define IFCVF_MDEV_LIMIT 1
> +
> +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */...
2019 Oct 16
0
[RFC 1/2] vhost: IFC VF hardware operation layer
...>
> +#include <linux/pci_regs.h>
> +#include <uapi/linux/virtio_net.h>
> +#include <uapi/linux/virtio_config.h>
> +#include <uapi/linux/virtio_pci.h>
> +
> +#define IFCVF_VENDOR_ID 0x1AF4
> +#define IFCVF_DEVICE_ID 0x1041
> +#define IFCVF_SUBSYS_VENDOR_ID 0x8086
> +#define IFCVF_SUBSYS_DEVICE_ID 0x001A
> +
> +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */
> +#define IFCVF_TRANSPORT_F_START 28...
2019 Nov 06
0
[PATCH 2/2] IFC VDPA layer
...cvf_destroy_adapter(adapter);
> + pci_free_irq_vectors(pdev);
> + pci_release_regions(pdev);
> + pci_disable_device(pdev);
> + kfree(adapter);
> +}
> +
> +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 },
> +};
> +MODULE_DEVICE_TABLE(pci, ifcvf_pci_ids);
> +
> +static struct pci_driver ifcvf_driver = {
> + .name = IFCVF_DRIVER_NAME,
> + .id_table = ifcvf_pci_ids,
> + .probe = ifcvf_probe,
> + .remove = ifcvf_remove,...
2019 Oct 21
0
[RFC 1/2] vhost: IFC VF hardware operation layer
...; +#include <uapi/linux/virtio_net.h>
>>> +#include <uapi/linux/virtio_config.h>
>>> +#include <uapi/linux/virtio_pci.h>
>>> +
>>> +#define IFCVF_VENDOR_ID???????? 0x1AF4
>>> +#define IFCVF_DEVICE_ID???????? 0x1041
>>> +#define IFCVF_SUBSYS_VENDOR_ID? 0x8086
>>> +#define IFCVF_SUBSYS_DEVICE_ID? 0x001A
>>> +
>>> +/*
>>> + * Some ifcvf feature bits (currently bits 28 through 31) are
>>> + * reserved for the transport being used (eg. ifcvf_ring), the
>>> + * rest are per-device feature bits.
&g...