similar to: [PATCH] add MOVSX instr support to VMX MMIO decoder

Cleanup vmx vmexit handler. Current code doesn''t handle vmexits caused by triple fault, INIT, SIPI, etc, which are listed in IA32 Architecture System Programming Guide 2, Appendix I VMX Basic Exit Reasons, and calls __hvm_bug() when not handling such cases, actually domain crash should be good enough. Also various coding style cleanups. Signed-off-by: Xin Li <xin.b.li@intel.com>

Hi all, This is today''s nightly testing report; no new issue today. Most of case failures are due to bug #1183 and #1194 listed below. For bug #1194, the issue `Linux booting hangs with "hda: dma..." errors` got fixed on this c/s; but neither Windows nor Linux X can boot up with setting sdl=1 and opengl=1 if guest''s resolution is set as 800 * 600 or higher. Old

Better use of VMX execution controls MSR. Signed-off-by: Xin Li<xin.b.li@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

　　We meet a block issue in today''s nightly testing. Xen0 hang when we destroy a XenU guest. Block issue 1) xen0 hang when destroying a XenU guest http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=963 Thanks Yunfeng _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Memory mapped and port I/O is currently broken under VMX when the partition is running in VM8086 mode. The reason is that the instruction decoding support uses 32-bit opcode/address decodes rather 16-bit decodes. This patch fixes that. In addition, the patch adds support for the "stos" instruction decoding because this is a frequently used way to clear MMIO areas such as the screen. As

We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Cannot boot Four VMX at same time on IA32 host - Cannot boot Windows XP SP1/SP2 on IA32e host - Create IA32-PAE VMX on IA32e host will make VMX kernel panic - Create IA32 VMX on IA32e host will make VMX hang - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: -

- we used the C4/C5 (first prefix) byte instead of the apparent ModR/M one as the second prefix byte - early decoding normalized vex.reg, thus corrupting it for the main consumer (copy_REX_VEX()), resulting in #UD on the two-operand instructions we emulate Also add respective test cases to the testing utility plus - fix get_fpu() (the fall-through order was inverted) - add cpu_has_avx2,

Hi there, I have a question regarding the functionality of x86_emulate_memop (Xen 3.1) or x86_emulate (Xen 3.2) function. This function gets called from sh_page_fault() function which is invoked when Xen receives a page fault. Since I am not clear completely about the emulation operation performed by Xen, I have following questions with a below mentioned scenario? 1) Suppose I have a memory

hi, i was trying to enable the mmx code on mac os x. to get to that point one has to replace some inline assembler code: .balign 16 -> .p2align 4 and replace .rept .. .endr with #defines. but to makes things more complicated apple's GAS does not support movsx instructions and thus the following line does not work: " movsx %%di, %%edi \n\t" [ more details at

> Hmmm... wouldn''t it be nice if we didn''t have a bespoke, > buggy & incomplete emulator for hvm mmio. ;-) In the process of solving this one, I''ve got to (another) of the blocking points... At the moment, we translate the virtual address from the guest in the page-fault-handler to guest physical address via the gva_to_gpa() function in svm.c/vmx.c:

Fix PAE shadow on a machine with RAM above 4G on x86_64 xen. Currently, on a machine with RAM above 4G, we can not run 32bit VMX guest on x86_64 xen, the root cause is that the PAE page table PDPT must below 4G, this patch fixes this issue. Also did some cleanup. Signed-off-by: Xin Li <xin.b.li@intel.com> Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>

The patch attached is to set effective memory type for EPT according to the VT-d snoop control capability, and also includes some cleansup for EPT & VT-d both enabled. Signed-off-by: Zhai, Edwin Edwin.Zhai@intel.com<mailto:Edwin.Zhai@intel.com> Signed-off-by: Xin, Xiaohui xiaohui.xin@intel.com<mailto:xiaohui.xin@intel.com> _______________________________________________

Hi guys, At a loss trying to figure why if (has_eflag(X86_EFLAGS_ID)) returns false in my HVM domU. Standard function has_eflag() in cpucheck.c running in real mode. Works fine on PV dom0, but fails when guest is booting on my hybrid dom0. LMK if any ideas. I''ll keep digging in the manuals, but nothing so far. thanks, Mukesh

Attached is a patch for shared interrupt between dom0 and HVM domain for vtd. Most of problem is caused by that we should inject interrupt to both domains and the physical interrupt deassertion then may be delayed by the device assigned to the HVM. The patch adds a timer, and the time out value is sufficient large to tolerant the delaying used to wait for the physical interrupt deassertion.

Currently, Xen does not support injecting an NMI to HVM guest OS. Adding this feature is necessary for those softwares which depend on NMI to function correctly, such as KDB and oprofile. The attached patch allows NMI to be injected to guest OS in NMIP capable platforms. It also enables to queue an NMI and then inject it as soon as possible. Signed-off-by: Haitao Shan

All, in the light of erratum #573 I''m wondering if we need to tweak or conditionally suppress fsincos emulation. The question is whether there is any possibility for getting the emulator to hit this instruction on AMD (as no real mode emulation ought to be taking place there), i.e. whether there are places where emulation gets continued eagerly in anticipation of the need for emulation

Hi all, This is today''s nightly testing report; no new issue found, bug #1259 got fixed. Some vt-d cases failed in first round testing, but can get pass in retesting. Fixed issue: ============================================== 1. booting windows guest causes Xen HV crash http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1259 Old issues:

Hi Keir, this patch changes common code of xen hypervisor, but seems we have to, because current call to do_boot_vcpu is always from domains, however, for SMP VMX guest AP bring up, we need call it from xen hypervisor, so we''d like to split it. What''s your opinion? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Jun suggested to use another elegant way, pls ignore this one. -Xin >SMP VMX guest AP bring up need call do_boot_vcpu in hypervisor. >Current call to do_boot_vcpu always from domain, however, for SMP VMX >guest AP bring up, it is called from xen hypervisor. >Signed-off-by: Xin Li <xin.b.li@intel.com> > >diff -r f069a06e650f xen/common/domain.c >--- a/xen/common/domain.c

Is it intentional that - under SVM, 32-bit guests can freely set EFER.LME - under VMX, 32-bit guests can''t access EFER at all? Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel