search for: gvec

...ellini <stefano.stabellini@eu.citrix.com> diff --git a/hw/pt-msi.c b/hw/pt-msi.c index f0fb3e3..b01744e 100644 --- a/hw/pt-msi.c +++ b/hw/pt-msi.c @@ -300,6 +300,14 @@ static int pt_msix_update_one(struct pt_dev *dev, int entry_nr) if ( !entry->flags ) return 0; + if (!gvec) { + /* if gvec is 0, the guest is asking for a particular pirq that + * is passed as dest_id */ + pirq = ((gaddr >> 32) & 0xffffff00) | + (((gaddr & 0xffffffff) >> MSI_TARGET_CPU_SHIFT) & 0xff); + PT_LOG("pt_msix_update_one re...

...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 pci_msix_writel: Can''t update entry 0 since MSI-X is already enabled (fee00000 -> fee02000)...

...dex=0 first_map=0 pt_ioport_map: e_phys=ffff pio_base=d000 len=256 index=0 first_map=0 pt_ioport_map: e_phys=c200 pio_base=d000 len=256 index=0 first_map=0 pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation pci_intx: intx=1 pt_msix_update_one: Update msix entry 0 with pirq 4d gvec 59 pci_msix_writel: Error: Can''t update msix entry 0 since MSI-X is already function. pci_msix_writel: Error: Can''t update msix entry 0 since MSI-X is already function. pci_msix_writel: Error: Can''t update msix entry 0 since MSI-X is already...

.../xen/pci.h | 3 ++- 6 files changed, 27 insertions(+), 5 deletions(-) diff --git a/tools/libxc/xc_domain.c b/tools/libxc/xc_domain.c index bb71cca..f6fc8e4 100644 --- a/tools/libxc/xc_domain.c +++ b/tools/libxc/xc_domain.c @@ -1339,7 +1339,9 @@ int xc_domain_update_msi_irq( uint32_t gvec, uint32_t pirq, uint32_t gflags, - uint64_t gtable) + uint64_t gtable, + uint16_t entry_nr, + uint32_t msi_ad[3]) { int rc; xen_domctl_bind_pt_irq_t *bind; @@ -1356,6 +1358,9 @@ int xc_domain_update_msi_irq( bind->u.msi.gvec = gvec; bind->u.msi.gflag...

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

pt_irq_create_bind_vtd() initializes this substructure only when setting .flags to HVM_IRQ_DPCI_MACH_MSI|HVM_IRQ_DPCI_GUEST_MSI (the PT_IRQ_TYPE_MSI case), while the other path will not set HVM_IRQ_DPCI_GUEST_MSI but may also set HVM_IRQ_DPCI_MACH_MSI. Yet hvm_dpci_msi_eoi() and hvm_migrate_pirqs() check for HVM_IRQ_DPCI_MACH_MSI, i.e. may run into an uninitialized .gmsi.* field. What am I missing

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 ?

Hi- I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device model. On boot I see the following error: MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h) A list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve

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