search for: subsys_vendor_id

Displaying 11 results from an estimated 11 matches for "subsys_vendor_id".

2014 Sep 21
2
[PATCH RFC] virtio-pci: share config interrupt between virtio devices
...e do set subsystem vendor ID properly for our virtio-pci devices? vpci->pci_hdr = (struct pci_device_header) { .vendor_id = cpu_to_le16(PCI_VENDOR_ID_REDHAT_QUMRANET), .device_id = cpu_to_le16(device_id), [...] .subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET), Thanks, Sasha
2014 Sep 21
2
[PATCH RFC] virtio-pci: share config interrupt between virtio devices
...e do set subsystem vendor ID properly for our virtio-pci devices? vpci->pci_hdr = (struct pci_device_header) { .vendor_id = cpu_to_le16(PCI_VENDOR_ID_REDHAT_QUMRANET), .device_id = cpu_to_le16(device_id), [...] .subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET), Thanks, Sasha
2014 Sep 21
1
[PATCH RFC] virtio-pci: share config interrupt between virtio devices
...;> > vpci->pci_hdr = (struct pci_device_header) { >> > .vendor_id = cpu_to_le16(PCI_VENDOR_ID_REDHAT_QUMRANET), >> > .device_id = cpu_to_le16(device_id), >> > [...] >> > .subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET), >> > >> > >> > Thanks, >> > Sasha > > Yes but the spec says: > The Subsystem Vendor ID should reflect the PCI Vendor ID of the environment. > > IOW lkvm shouldn't reuse the ID f...
2014 Sep 21
1
[PATCH RFC] virtio-pci: share config interrupt between virtio devices
...;> > vpci->pci_hdr = (struct pci_device_header) { >> > .vendor_id = cpu_to_le16(PCI_VENDOR_ID_REDHAT_QUMRANET), >> > .device_id = cpu_to_le16(device_id), >> > [...] >> > .subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET), >> > >> > >> > Thanks, >> > Sasha > > Yes but the spec says: > The Subsystem Vendor ID should reflect the PCI Vendor ID of the environment. > > IOW lkvm shouldn't reuse the ID f...
2014 Sep 21
0
[PATCH RFC] virtio-pci: share config interrupt between virtio devices
...roperly for our virtio-pci devices? > > vpci->pci_hdr = (struct pci_device_header) { > .vendor_id = cpu_to_le16(PCI_VENDOR_ID_REDHAT_QUMRANET), > .device_id = cpu_to_le16(device_id), > [...] > .subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET), > > > Thanks, > Sasha Yes but the spec says: The Subsystem Vendor ID should reflect the PCI Vendor ID of the environment. IOW lkvm shouldn't reuse the ID from qemu, it should have its own (qemu and lkvm hypervisors...
2014 Sep 18
3
[PATCH RFC] virtio-pci: share config interrupt between virtio devices
On Monday 01 September 2014 09:37:30, Michael S. Tsirkin wrote: > Why do we need INT#x? > How about setting IRQF_SHARED for the config interrupt > while using MSI-X? You'd have to read ISR to check that the > interrupt was intended for your device. The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I don't think that you can depend on the device to
2014 Sep 18
3
[PATCH RFC] virtio-pci: share config interrupt between virtio devices
On Monday 01 September 2014 09:37:30, Michael S. Tsirkin wrote: > Why do we need INT#x? > How about setting IRQF_SHARED for the config interrupt > while using MSI-X? You'd have to read ISR to check that the > interrupt was intended for your device. The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I don't think that you can depend on the device to
2008 May 16
19
[Bug 15949] New: LVDS-0 has wrapped screen with Randr1.2
...pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:05.0' (string) pci.product = 'C51 [Geforce 6150 Go]' (string) pci.product_id = 580 (0x244) (int) pci.subsys_product_id = 12479 (0x30bf) (int) pci.subsys_vendor = 'Hewlett-Packard Company' (string) pci.subsys_vendor_id = 4156 (0x103c) (int) pci.vendor = 'nVidia Corporation' (string) pci.vendor_id = 4318 (0x10de) (int) [snip] -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
2023 Apr 27
4
[RFC PATCH v2 0/3] Introduce a PCIe endpoint virtio console
PCIe endpoint framework provides APIs to implement PCIe endpoint function. This framework allows defining various PCIe endpoint function behaviors in software. This patch extend the framework for virtio pci device. The virtio is defined to communicate guest on virtual machine and host side. Advantage of the virtio is the efficiency of data transfer and the conciseness of implementation device
2015 Nov 18
2
[RFC] kvmtool: add support for modern virtio-pci
...MRANET), + .device_id = cpu_to_le16(device_id), + .command = PCI_COMMAND_IO | PCI_COMMAND_MEMORY, + .header_type = PCI_HEADER_TYPE_NORMAL, + .revision_id = 0, + .class[0] = class & 0xff, + .class[1] = (class >> 8) & 0xff, + .class[2] = (class >> 16) & 0xff, + .subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET), + .subsys_id = cpu_to_le16(subsys_id), + .bar[0] = cpu_to_le32(vpci->mmio_addr + | PCI_BASE_ADDRESS_SPACE_MEMORY), + .bar[1] = cpu_to_le32(vpci->port_addr + | PCI_BASE_ADDRESS_SPACE_IO), + .bar[2] = cpu_to_le32(vpc...
2015 Nov 18
2
[RFC] kvmtool: add support for modern virtio-pci
...MRANET), + .device_id = cpu_to_le16(device_id), + .command = PCI_COMMAND_IO | PCI_COMMAND_MEMORY, + .header_type = PCI_HEADER_TYPE_NORMAL, + .revision_id = 0, + .class[0] = class & 0xff, + .class[1] = (class >> 8) & 0xff, + .class[2] = (class >> 16) & 0xff, + .subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET), + .subsys_id = cpu_to_le16(subsys_id), + .bar[0] = cpu_to_le32(vpci->mmio_addr + | PCI_BASE_ADDRESS_SPACE_MEMORY), + .bar[1] = cpu_to_le32(vpci->port_addr + | PCI_BASE_ADDRESS_SPACE_IO), + .bar[2] = cpu_to_le32(vpc...