search for: msi_bus

...> new MSI setup framework, as you mentioned before, in device-driver model. > > I abstracted a new virtual device (called struct msi_dev), this msi_dev will > manage all MSI info, Will this "struct msi_dev" will be part of "struct device"? > and a new bus named msi_bus, also introduced a new driver > msi_driver, msi_bus is responsible for binding msi_dev and msi_driver. > All MSI devices will be classified into different MSI device types, like > MSI_TYPE_PCI, MSI_TYPE_HPET, MSI_TYPE_DMAR, etc.. > > Each MSI type device should provide a private str...

...> new MSI setup framework, as you mentioned before, in device-driver model. > > I abstracted a new virtual device (called struct msi_dev), this msi_dev will > manage all MSI info, Will this "struct msi_dev" will be part of "struct device"? > and a new bus named msi_bus, also introduced a new driver > msi_driver, msi_bus is responsible for binding msi_dev and msi_driver. > All MSI devices will be classified into different MSI device types, like > MSI_TYPE_PCI, MSI_TYPE_HPET, MSI_TYPE_DMAR, etc.. > > Each MSI type device should provide a private str...

...SI devices are always on a bus. The existing HPET, DMAR device both have no bus bind. I'm working on a new MSI setup framework, as you mentioned before, in device-driver model. I abstracted a new virtual device (called struct msi_dev), this msi_dev will manage all MSI info, and a new bus named msi_bus, also introduced a new driver msi_driver, msi_bus is responsible for binding msi_dev and msi_driver. All MSI devices will be classified into different MSI device types, like MSI_TYPE_PCI, MSI_TYPE_HPET, MSI_TYPE_DMAR, etc.. Each MSI type device should provide a private struct msi_driver. msi_drive...

Hi Yijing > -----Original Message----- > From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org] > On Behalf Of Yijing Wang > Sent: Monday, August 04, 2014 8:34 AM > To: Basu Arnab-B45036 > Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org; > Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm- > kernel at

Hi Yijing > -----Original Message----- > From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org] > On Behalf Of Yijing Wang > Sent: Monday, August 04, 2014 8:34 AM > To: Basu Arnab-B45036 > Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org; > Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm- > kernel at

...t supports 1 MSI vector, so I think this >>> card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. >>> >>> You can check PCI bus whether support MSI like: >>> >>> cat /sys/bus/pci/devices/00:0e.0/msi_bus >>> >>> Other, do you call pci_enable_device() before pci_enable_msi() ? >> >> Yes, the device is enabled. nouveau does generally work for most >> people :) And it works fine here if MSI is forced off. >> >> The problem here is that pci_enable_msi() s...

...t; ATTRS{class}=="0x000000" ATTRS{driver_override}=="(null)" ATTRS{consistent_dma_mask_bits}=="64" ATTRS{dma_mask_bits}=="64" ATTRS{local_cpus}=="3" ATTRS{device}=="0x1004" ATTRS{enable}=="1" ATTRS{msi_bus}=="" ATTRS{local_cpulist}=="0-1" ATTRS{vendor}=="0x1af4" ATTRS{subsystem_device}=="0x0008" ATTRS{numa_node}=="-1" ATTRS{d3cold_allowed}=="0" looking at parent device '/devices/pci0000:00': KERNELS=="...

> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one > computer using megatec_usb driver. But megatec_usb completly ignores port > directive in ups.conf, I even try port = /dev/null and megatec_usb founds > ups and it works. The 'port' is not used for USB connected devices, it's only needed for compatibility reasons. > Problem is that

Hi everyone, after following in the footsteps of the following discussion (http://lists.xenproject.org/archives/html/xen-users/2013-09/msg00106.html) I had been able to turn my GTX 480 into a Quadro 6000. When I VT-d passthrough it to a Debian jessie VM it shows up fine and CUDA 5.5 seems to function properly up to a point: lspci -v: 00:04.0 VGA compatible controller: NVIDIA Corporation GF100GL

...- 1 root root 4096 Nov 13 17:37 enable -r--r--r-- 1 root root 4096 Oct 16 15:25 irq -r--r--r-- 1 root root 4096 Nov 13 17:37 local_cpulist -r--r--r-- 1 root root 4096 Nov 13 17:37 local_cpus -r--r--r-- 1 root root 4096 Nov 13 17:37 modalias -rw-r--r-- 1 root root 4096 Nov 13 17:37 msi_bus -r--r--r-- 1 root root 4096 Nov 13 17:37 numa_node drwxr-xr-x 2 root root 0 Nov 13 17:37 power --w--w---- 1 root root 4096 Nov 13 17:37 remove --w--w---- 1 root root 4096 Nov 13 17:37 rescan --w------- 1 root root 4096 Nov 13 17:37 reset -r--r--r-- 1 root root 4096 Oct 16 15:25...

...tor, so I think this >>>> card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. >>>> >>>> You can check PCI bus whether support MSI like: >>>> >>>> cat /sys/bus/pci/devices/00:0e.0/msi_bus >>>> >>>> Other, do you call pci_enable_device() before pci_enable_msi() ? >>> >>> Yes, the device is enabled. nouveau does generally work for most >>> people :) And it works fine here if MSI is forced off. >>> >>> The problem her...

..._node? reset????? resource0_wc? subsystem ?uevent > class???????????????? d3cold_allowed??????????? driver?????????? irq > modalias??? physfn???? resource?? resource3???? subsystem_device ?vendor > config??????????????? device??????????????????? driver_override local_cpulist > msi_bus???? power????? resource0? resource3_wc subsystem_vendor > > >> If bound to xen-pciback, it vf should also appear in the output of 'xl >> pci-assignable-list'. > > Before starting the VM, it's there: > > [root at xengfs1f ~]# xl pci-assignable-list | gr...

On Fri, Apr 24, 2020 at 4:35 PM Peter Crowther <peter.crowther@melandra.com> wrote: > > On Fri, 24 Apr 2020 at 21:10, Mauricio Tavares <raubvogel@gmail.com> wrote: >> >> Let's say I have libvirt >> >> [root@vmhost2 ~]# virsh version >> [...] >> >> Running hypervisor: QEMU 2.12.0 >> [root@vmhost2 ~]# >> [...] > > When

Yijing, cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting that it supports MSI. However, this "00:0e.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" is a component of the addin card. Wouldn't the lack of support for MSI by the chipset "00:00.0 Host bridge: Intel Corporation 43...

On 2014/7/4 10:45, Brian Becker wrote: > Yijing, > > cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting > that it supports MSI. However, this "00:0e.0 PCI bridge: PLX > Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" > is a component of the addin card. Wouldn't the lack of support for MSI > by the chipset "00:00.0 Host bridge:...

...atible controller PCI config register, it supports 1 MSI vector, so I think this > card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. > > You can check PCI bus whether support MSI like: > > cat /sys/bus/pci/devices/00:0e.0/msi_bus > > Other, do you call pci_enable_device() before pci_enable_msi() ? Yes, the device is enabled. nouveau does generally work for most people :) And it works fine here if MSI is forced off. The problem here is that pci_enable_msi() succeeds, but it probably shouldn't. I don't know al...

...>>>>> card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. >>>>> >>>>> You can check PCI bus whether support MSI like: >>>>> >>>>> cat /sys/bus/pci/devices/00:0e.0/msi_bus >>>>> >>>>> Other, do you call pci_enable_device() before pci_enable_msi() ? >>>> >>>> Yes, the device is enabled. nouveau does generally work for most >>>> people :) And it works fine here if MSI is forced off. >>>> >...

I mistakenly only replied to Yijing Wang the first time. Here are the further details. uname -a: Linux p5-133 3.15.2-p5-133 #1 Thu Jun 26 22:56:27 EDT 2014 i586 GNU/Linux Here is the output from lspci -vvvxxx: root at p5-133:~# cat lspci.txt 00:00.0 Host bridge: Intel Corporation 430FX - 82437FX TSC [Triton I] (rev 01) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

...m your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. You can check PCI bus whether support MSI like: cat /sys/bus/pci/devices/00:0e.0/msi_bus Other, do you call pci_enable_device() before pci_enable_msi() ? On 2014/7/4 8:35, Brian Becker wrote: > I mistakenly only replied to Yijing Wang the first time. Here are the further details. > > uname -a: Linux p5-133 3.15.2-p5-133 #1 Thu Jun 26 22:56:27 EDT 2014 i586 GNU/Linux > &...

...I config register, it supports 1 MSI vector, so I think this >> card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. >> >> You can check PCI bus whether support MSI like: >> >> cat /sys/bus/pci/devices/00:0e.0/msi_bus >> >> Other, do you call pci_enable_device() before pci_enable_msi() ? > > Yes, the device is enabled. nouveau does generally work for most > people :) And it works fine here if MSI is forced off. > > The problem here is that pci_enable_msi() succeeds, but it probably I...