search for: pci_intx

This fixes a few things that I missed in previous patches: * Use the hw INTX rather than INTA in pt_reset_interrupt_and_io_mapping() This is consistent with other uses of pci_intx() * Remove now inaccurate "/* fix virtual interrupt pin to INTA# */" comments * Use PCI_SLOT() Signed-off-by: Simon Horman <horms@verge.net.au> Index: ioemu-remote/hw/pass-through.c =================================================================== --- ioemu-remote.orig/hw/pass-t...

...on registered (size=0x10000000 base_addr=0xd000000c) pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfba20004) pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000a001) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xfba00002) pci_intx: intx=1 register_real_device: Real physical device 03:00.0 registered successfuly! IRQ type = INTx dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 03:00.1 ... pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No such fi...

...0 0 0 PCI-MSI-edge mpt2sas0-msix0 After change affinity to vcpu1, interrupt still happen on vcpu0. And sometimes we got "/No irq handler for vector (irq -1)/" and panic. qemu-dm.log shows error: pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation pci_intx: intx=1 pt_msi_disable: Unmap msi with pirq 4f pt_msix_update_one: Update msix entry 0 with pirq 4f gvec 59 pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation pci_intx: intx=1 pt_msi_disable: Unmap msi with pirq 4e pt_msix_update_one: Update msix entry 0 with pirq 4e gvec 69...

...gister_regions: Expansion ROM registered (size=0x00080000 base_addr=0xdf080000) pt_msix_init: get MSI-X table bar base df03c000 pt_msix_init: table_off = 2000, total_entries = 15 pt_msix_init: errno = 2 pt_msix_init: mapping physical MSI-X table to 7fd7738ea000 pt_msi_setup: msi mapped with pirq 4f pci_intx: intx=1 register_real_device: Real physical device 0d:00.0 registered successfuly! IRQ type = MSI-INTx dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 1f:00.0 ... register_real_device: Enable MSI translation via per device option register_real_devic...

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that

On 12/03/2015 06:21, Fam Zheng wrote: > If the device doesn't support shutdown, disabling interrupts may cause > trouble. For example, virtio-scsi-pci doesn't implement shutdown, and > after we disable MSI-X, futher notifications from device will be > delivered to IRQ, which is unexpected. This IRQ will not be cleared, and > may prevent us from making progress, by keep

On 12/03/2015 06:21, Fam Zheng wrote: > If the device doesn't support shutdown, disabling interrupts may cause > trouble. For example, virtio-scsi-pci doesn't implement shutdown, and > after we disable MSI-X, futher notifications from device will be > delivered to IRQ, which is unexpected. This IRQ will not be cleared, and > may prevent us from making progress, by keep

...diff --git a/include/linux/pci.h b/include/linux/pci.h index 7cb0084..31d8a12 100644 --- a/include/linux/pci.h +++ b/include/linux/pci.h @@ -780,7 +780,11 @@ int __must_check pci_set_mwi(struct pci_dev *dev); int pci_try_set_mwi(struct pci_dev *dev); void pci_clear_mwi(struct pci_dev *dev); void pci_intx(struct pci_dev *dev, int enable); +#ifdef CONFIG_PCI_MSI void pci_msi_off(struct pci_dev *dev); +#else +static inline void pci_msi_off(struct pci_dev *dev) {} +#endif int pci_set_dma_max_seg_size(struct pci_dev *dev, unsigned int size); int pci_set_dma_seg_boundary(struct pci_dev *dev, unsigned...

...diff --git a/include/linux/pci.h b/include/linux/pci.h index 7cb0084..31d8a12 100644 --- a/include/linux/pci.h +++ b/include/linux/pci.h @@ -780,7 +780,11 @@ int __must_check pci_set_mwi(struct pci_dev *dev); int pci_try_set_mwi(struct pci_dev *dev); void pci_clear_mwi(struct pci_dev *dev); void pci_intx(struct pci_dev *dev, int enable); +#ifdef CONFIG_PCI_MSI void pci_msi_off(struct pci_dev *dev); +#else +static inline void pci_msi_off(struct pci_dev *dev) {} +#endif int pci_set_dma_max_seg_size(struct pci_dev *dev, unsigned int size); int pci_set_dma_seg_boundary(struct pci_dev *dev, unsigned...

...on registered (size=0x10000000 base_addr=0xd000000c) pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfe7f0004) pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000d001) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xfe7c0002) pci_intx: intx=1 register_real_device: Real physical device 03:00.0 registered successfuly! I''m using Xen 4.2.1 and xl toolstack. I have the following in VM config file: builder = "hvm" gfx_passthru = 1 pci = [''03:00.0'',''03:00.1''] vm config file: ful...

...ice: Disable MSI translation via per device option register_real_device: Disable power management pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x14.0x2 pt_register_regions: IO region registered (size=0x00004000 base_addr=0xfeb00004) pci_intx: intx=1 register_real_device: Real physical device 00:14.2 registered successfuly! IRQ type = INTx ... [jason@virt-host ~]$ lspci -tv -[0000:00]-+-00.0 ATI Technologies Inc RD890 PCI to PCI bridge (external gfx0 port B) +-00.2 ATI Technologies Inc Device 5a23 +-02.0-[01]--+...

Hi, everyone! I am working on xen-4.2.0 with spice remote connect. My host is Fedora 14 and guest is win7. I have installed spice package and now I can connect to guest by spice client. For better graphics experience, I want to try the VGA passthrough. With spice tool, I have to create a VM by xl command, and now I am wondering if it supports VGA passghrouth? If so, how should I test it ?

...ry(struct pci_dev *dev) +static struct msi_desc *alloc_msi_entry(struct msi_irqs *msi) { struct msi_desc *desc = kzalloc(sizeof(*desc), GFP_KERNEL); if (!desc) return NULL; INIT_LIST_HEAD(&desc->list); - desc->dev = dev; + desc->msi = msi; return desc; } -static void pci_intx_for_msi(struct pci_dev *dev, int enable) +static void pci_intx_for_msi(struct msi_irqs *msi, int enable) { + struct pci_dev *dev = msi->data; + if (!(dev->dev_flags & PCI_DEV_FLAGS_MSI_INTX_DISABLE_BUG)) pci_intx(dev, enable); } @@ -444,9 +473,9 @@ static void __pci_restore_msi_sta...

Hello I am new in XEN and Linux. I am trying the VGA passthru. I can xen-pciback.hide EtherNet, Serial Com port. But when I xen-pciback.hide my VGA. I can no longer login to the Linux(Fedora 12). Then how can I xm create a XP DomU guest? Can anyone help? I am using Intel Q35 MB with Intel Core2 CPU. _______________________________________________ Xen-users mailing list

...ry(struct msi_irqs *msi) > { > struct msi_desc *desc = kzalloc(sizeof(*desc), GFP_KERNEL); > if (!desc) > return NULL; > > INIT_LIST_HEAD(&desc->list); > - desc->dev = dev; > + desc->msi = msi; > > return desc; > } > > -static void pci_intx_for_msi(struct pci_dev *dev, int enable) > +static void pci_intx_for_msi(struct msi_irqs *msi, int enable) > { > + struct pci_dev *dev = msi->data; > + > if (!(dev->dev_flags & PCI_DEV_FLAGS_MSI_INTX_DISABLE_BUG)) > pci_intx(dev, enable); > } > @@ -444,9 +47...

...ry(struct msi_irqs *msi) > { > struct msi_desc *desc = kzalloc(sizeof(*desc), GFP_KERNEL); > if (!desc) > return NULL; > > INIT_LIST_HEAD(&desc->list); > - desc->dev = dev; > + desc->msi = msi; > > return desc; > } > > -static void pci_intx_for_msi(struct pci_dev *dev, int enable) > +static void pci_intx_for_msi(struct msi_irqs *msi, int enable) > { > + struct pci_dev *dev = msi->data; > + > if (!(dev->dev_flags & PCI_DEV_FLAGS_MSI_INTX_DISABLE_BUG)) > pci_intx(dev, enable); > } > @@ -444,9 +47...

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

...cy interrupts. + * + * @mdev: pointer to mic_device instance + * + * RETURNS: An appropriate -ERRNO error value on error, or zero for success. + */ +static int mic_setup_intx(struct mic_device *mdev) +{ + struct pci_dev *pdev = mdev->pdev; + int rc; + + pci_msi_off(pdev); + + /* Enable intx */ + pci_intx(pdev, 1); + + rc = mic_setup_callbacks(mdev); + if (rc) { + dev_err(&pdev->dev, "Error setting up callbacks\n"); + goto err_nomem; + } + + rc = request_irq(pdev->irq, mic_interrupt, + IRQF_SHARED, "mic-intx", mdev); + if (rc) + goto err; + + dev_dbg(&pdev->d...

Hi all, The series is a draft of generic MSI driver that supports PCI and Non-PCI device which have MSI capability. If you're not interested it, sorry for the noise. The series is based on Linux-3.16-rc1. MSI was introduced in PCI Spec 2.2. Currently, kernel MSI driver codes are bonding with PCI device. Because MSI has a lot advantages in design. More and more non-PCI devices want to use