search for: vmsi

...hich means Xen doesn''t clear the mask bit in hardware for the MSI-X interrupt, so it remains disabled, that is why it loses the network connection. This patch fixes this issue. Signed-off-by: Feng Wu <feng.wu@intel.com> --- xen/arch/x86/hvm/io.c | 3 +++ xen/arch/x86/hvm/vmsi.c | 18 ++++++++++++++++++ xen/include/asm-x86/domain.h | 8 ++++++++ xen/include/xen/pci.h | 1 + 4 files changed, 30 insertions(+), 0 deletions(-) diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c index deb7b92..6c83c25 100644 --- a/xen/arch/x86/hvm/io.c +++ b/xen/ar...

...ich means Xen doesn''t clear the mask bit in hardware for the MSI-X interrupt, so it remains disabled, that is why it loses the network connection. This patch fixes this issue. Signed-off-by: Feng Wu <feng.wu@intel.com> --- xen/arch/x86/hvm/io.c | 4 ++++ xen/arch/x86/hvm/vmsi.c | 15 +++++++++++++++ xen/include/asm-x86/domain.h | 7 +++++++ xen/include/xen/pci.h | 1 + 4 files changed, 27 insertions(+), 0 deletions(-) diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c index deb7b92..bd751d1 100644 --- a/xen/arch/x86/hvm/io.c +++ b/xen/arch/x...

...bit is 0 v4: Added a warning if Xen thinks MSI-X control bit is masked, where in reality, it''s not v5 & v6: Added const-correctness v7: Get msi_desc from the guest write ''address'' Signed-off-by: Joby Poriyath <joby.poriyath@citrix.com> --- xen/arch/x86/hvm/vmsi.c | 73 +++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 61 insertions(+), 12 deletions(-) diff --git a/xen/arch/x86/hvm/vmsi.c b/xen/arch/x86/hvm/vmsi.c index 0d5ef1b..6830cf2 100644 --- a/xen/arch/x86/hvm/vmsi.c +++ b/xen/arch/x86/hvm/vmsi.c @@ -187,6 +187,19 @@ static struct ms...

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 mode setting to root-cause the issue. But I''m not an xen developer, and am even a newbie as a xen us...

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

...interrupt capability VMX: Turn on posted interrupt bit in vmcs VMX: Add posted interrupt supporting VMX: Use posted interrupt to deliver virutal interrupt xen/arch/x86/hvm/vioapic.c | 4 +- xen/arch/x86/hvm/vlapic.c | 19 +++++- xen/arch/x86/hvm/vmsi.c | 5 +- xen/arch/x86/hvm/vmx/vmcs.c | 18 +++++- xen/arch/x86/hvm/vmx/vmx.c | 81 ++++++++++++++++++++++++ xen/arch/x86/hvm/vmx/vpmu_core2.c | 5 +- xen/arch/x86/hvm/vpt.c | 10 ++- xen/...

...inded in qemu side. Kernel will get wrong value when reading msix info. Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com> Tested-by: Yuval Shaia <yuval.shaia@oracle.com> --- tools/libxc/xc_domain.c | 7 ++++++- tools/libxc/xenctrl.h | 4 +++- xen/arch/x86/hvm/vmsi.c | 13 ++++++++++++- xen/drivers/passthrough/io.c | 3 ++- xen/include/public/domctl.h | 2 ++ xen/include/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 ---...

.../x86/hpet.c +++ b/xen/arch/x86/hpet.c @@ -312,7 +312,7 @@ static void __hpet_setup_msi_irq(struct { struct msi_msg msg; - msi_compose_msg(desc->irq, &msg); + msi_compose_msg(desc, &msg); hpet_msi_write(desc->action->dev_id, &msg); } --- a/xen/arch/x86/hvm/vmsi.c +++ b/xen/arch/x86/hvm/vmsi.c @@ -382,7 +382,7 @@ int msixtbl_pt_register(struct domain *d return r; } - if ( irq_desc->handler != &pci_msi_type ) + if ( !irq_desc->msi_desc ) goto out; msi_desc = irq_desc->msi_desc; @@ -426,7 +426,7 @@ void msix...

...; Acked-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25092:a66fb91cb8d3 xen-unstable date: Fri Mar 23 08:39:39 2012 +0100 changeset: 21579:7d704b95c0ef user: Keir Fraser <keir@xen.org> date: Fri Mar 23 13:55:40 2012 +0000 vMSI: fix ia64 build for 21577:c41ab909f08e On ia64, 21577:c41ab909f08e introduces the following error: /xen/include/xen/pci.h:52: warning: implicit declaration of function `PFN_UP'' /xen/include/xen/pci.h:52: error: variable-size type declared outside of any fun...

...control bit is masked, where in reality, it''s not v5 & v6: Added const-correctness v7: Get msi_desc from the guest write ''address'' v8: Added ASSERT and renamed m_desc to msi_desc Signed-off-by: Joby Poriyath <joby.poriyath@citrix.com> --- xen/arch/x86/hvm/vmsi.c | 75 +++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 63 insertions(+), 12 deletions(-) diff --git a/xen/arch/x86/hvm/vmsi.c b/xen/arch/x86/hvm/vmsi.c index 0d5ef1b..1f43f6b 100644 --- a/xen/arch/x86/hvm/vmsi.c +++ b/xen/arch/x86/hvm/vmsi.c @@ -187,6 +187,19 @@ static struct ms...

...n=f3040 mfn=f7c40 nr=4 (XEN) irq.c:270: Dom14 PCI link 0 changed 5 -> 0 (XEN) irq.c:270: Dom14 PCI link 1 changed 10 -> 0 (XEN) irq.c:270: Dom14 PCI link 2 changed 11 -> 0 (XEN) irq.c:270: Dom14 PCI link 3 changed 5 -> 0 (XEN) irq.c:2234: dom14: pirq 51 or emuirq 23 already mapped (XEN) vmsi.c:108:d32767 Unsupported delivery mode 3 (XEN) emulate.c:88:d14 bad mmio size 16 (XEN) io.c:199:d14 MMIO emulation failed @ 0033:7fa98cc628b4: 66 0f 7f 0f 0f 28 56 10 0f 29 (XEN) stdvga.c:147:d14 entering stdvga and caching modes (XEN) stdvga.c:151:d14 leaving stdvga (XEN) emulate.c:88:d14 bad mmio...

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

What are the outstanding things to do before we think we can start on the 4.2 -rc''s? Does anyone have a timetable in mind? hypervisor: * ??? - Keir, Tim, Jan? tools: * libxl stable API -- we would like 4.2 to define a stable API which downstream''s can start to rely on not changing. Aspects of this are: * event handling (IanJ working