search for: vmx_vmexit_handler

Hi, Keir, This patch is to fix the problem of Linux guest installation failure and Windows 2000 boot failure.       In the early code, we use vmx_vmexit_handler() -> vmx_io_instruction() function to emulate I/O instructions. But now, we use vmx_vmexit_handler() -> handle_mmio -> hvm_emulate_one() -> x86_emulate() to emulate I/O instructions. Also nowadays, the realmode emulation code walks through the path: vmx_realmode() -> realmode_emulate...

Hi I am using oprofile 0.9.3 on xen cs 16540 on an Intel system. When I look at the top "hot" functions, I see p2m_change_type being one of the top function in xen-syms. This function is only in the svm (AMD) code and should not appear on an Intel system. I see that this function is not being clled at all when I am running my apps as I have put printk in the functions and they do

...t the call trace reads as follows: (XEN) Xen call trace: (XEN) [<ffff82c4801e1be9>] ept_get_entry+0x13a/0x28f (XEN) [<ffff82c4801da274>] __get_gfn_type_access+0x175/0x256 (XEN) [<ffff82c4801b5a55>] hvm_hap_nested_page_fault+0x133/0x422 (XEN) [<ffff82c4801d3c8e>] vmx_vmexit_handler+0x136b/0x1614 The entire log from boot to crash can be viewed at the following link: http://pastebin.com/5wcH7GWR Here''s the kernel''s config http://pastebin.com/E51S61Qk And although I''m not sure if knowing BIOS settings is useful it doesn''t hurt to share the...

...t; -- Changes since v2 * Switch from ''int $2'' to do_nmi() * Reworked commit message to more clearly explain the problem diff -r 2489c2926698 -r d7ea938044ac xen/arch/x86/hvm/vmx/vmx.c --- a/xen/arch/x86/hvm/vmx/vmx.c +++ b/xen/arch/x86/hvm/vmx/vmx.c @@ -2269,6 +2269,14 @@ void vmx_vmexit_handler(struct cpu_user_ vector = intr_info & INTR_INFO_VECTOR_MASK; if ( vector == TRAP_machine_check ) do_machine_check(regs); + else if ( vector == TRAP_nmi && + ( (intr_info & INTR_INFO_INTR_TYPE_MASK) == + (X86_EVENT...

>Since this happens early in HVM guest boot, I suggest adding tracing to >vmx_vmexit_handler() to dump registers on every MSR write. >Something like >this early on in the function: > if ( reason == EXIT_REASON_MSR_WRITE ) { > printk("regs==%p, guest_regs==%p\n", &regs, >guest_cpu_user_regs()); > show_registers(&regs); > } > >This will...

...;'perf top'' within an SMP PVHVM guest, after a couple of seconds or minutes the guest hangs. Hypervisor ends up stuck too looping, and then the dom0 ends up hanging as well. Dumping the cpu registers (Ctrl-A x3, then ''d'' shows that the guest is pretty firmly stuck in vmx_vmexit_handler: (XEN) [<ffff82c4c01d386f>] vmx_vmexit_handler+0x22f/0x174 and if I let this stay for some time, dom0 detects that some of its VCPUs are hanged and it resorts to sending NMI. NMI is not implemented in pv-ops and then dom0 wedges. In some cases it also wedges itself when doing ''x...

hello list: I add some code to xen-3.1.0-src\xen\arch\x86\hvm\vmx\vmx.c to export some information when vmx_vmexit_handler() executed: ------------------------------------------------------------------------------------------------- --- vmx.c 2007-05-18 22:45:22.000000000 +0800 +++ vmx-patch.c 2008-11-24 14:19:18.000000000 +0800 @@ -50,7 +50,9 @@ #include <asm/hvm/vpt.h> #include <public/hvm/save.h> #in...

Hi, --- background ---------------------------------------------------- * what the makedumpfile is: To shorten the size of the dumpfile and the time of creating the dumpfile, makedumpfile copies only the necessary pages for analysis to the dumpfile from /proc/vmcore. You can specify the kind of unnecessary pages with dump_level. If you want to shorten the size further, enable the

...mx_world_save: 1040 0xffff830000106800 do_dom0_op: 968 0xffff8300001080cf do_dom0_op: 968 0xffff830000137c64 construct_dom0: 968 0xffff83000013a81e construct_dom0: 968 0xffff8300001b1dbc vmx_vmexit_handler: 632 0xffff8300001b2f58 vmx_vmexit_handler: 632 0xffff8300001313ff arch_do_dom0_op: 552 0xffff8300001327f3 arch_do_dom0_op: 552 0xffff830000158660 emulate_privileged_op: 520 0xffff83000015a06c emulate_privileged...

Changes from v1: - Define new struct hvm_trap to represent information of trap, include instruction length. - Renames hvm_inject_exception to hvm_inject_trap. Then define a couple of wrappers around that function for existing callers, so that their parameter lists actually *shrink*. This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP),

..._SW_EXCEPTION; /* into; CE */ + break; + default: - if ( trap > TRAP_last_reserved ) - { - type = X86_EVENTTYPE_SW_EXCEPTION; - __vmwrite(VM_ENTRY_INSTRUCTION_LEN, 2); /* int imm8 */ - } break; } @@ -2447,6 +2457,11 @@ void vmx_vmexit_handler(struct cpu_user_ if ( handled < 0 ) { vmx_inject_exception(TRAP_int3, HVM_DELIVER_NO_ERROR_CODE, 0); + /* + * According to the vmx_inject_hw_exception() description, + * it must set...

...y reads from these registers as I''d expect when sysenter is called. My goal is to capture when the execution jumps to guest kernel space either through a system call or any other interrupt/exception. Is there a way I can capture the privilege escalation? I''m mainly looking into vmx_vmexit_handler, but I''m not even sure if the events I''m looking for trigger VMEXITs. Thanks in advance. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...n "Virtual Interrupt Delivery" is enabled, this function is used + * to handle EOI-induced VM exit + */ +void vmx_handle_EOI_induced_exit(struct vlapic *vlapic, int vector) +{ + ASSERT(cpu_has_vmx_virtual_intr_delivery); + + vlapic_handle_EOI_induced_exit(vlapic, vector); +} + void vmx_vmexit_handler(struct cpu_user_regs *regs) { unsigned int exit_reason, idtv_info, intr_info = 0, vector = 0; @@ -2677,6 +2706,16 @@ void vmx_vmexit_handler(struct cpu_user_ hvm_inject_hw_exception(TRAP_gp_fault, 0); break; + case EXIT_REASON_EOI_INDUCED: + { + int vector...

...RY_VM_EXEC_CONTROL, v->arch.hvm_vmx.secondary_exec_control); Index: hv/xen/arch/x86/hvm/vmx/vmx.c =================================================================== --- hv.orig/xen/arch/x86/hvm/vmx/vmx.c +++ hv/xen/arch/x86/hvm/vmx/vmx.c @@ -2617,6 +2617,13 @@ asmlinkage void vmx_vmexit_handler(struc break; } + case EXIT_REASON_PAUSE_INSTRUCTION: + { + perfc_incr(ple_exits); + do_sched_op_compat(SCHEDOP_yield, 0); + break; + } + default: exit_and_crash: gdprintk(XENLOG_ERR, "Bad vmexit (reason %x)\n", exit_reason);...

...ime virtualization. Please let me show you the whole process: 1 Phenomenon when I run a JVM based program in IE browser in my Virtual Machine, I have found clearly that time at the right bottom corner in my VM gets more slower and slower. I studied the bug deeply, and found something below. 2 Xen vmx_vmexit_handler --> ......... --> handle_rtc_io --> rtc_ioport_write --> rtc_timer_update --> set RTC's REG_A to a high rate--> create_periodic_time(disable the former timer, and init a new one) Win7 is installed in the vm. This calling path is executed so frequent that may come down to se...

...->arch.hvm_vcpu.guest_efer & EFER_LMA) ) return; - if ( cr3 & 0x1fUL ) + if ( (cr3 & 0x1fUL) && !hvm_pcid_enabled(v) ) goto crash; mfn = mfn_x(gfn_to_mfn(v->domain, cr3 >> PAGE_SHIFT, &p2mt)); @@ -2661,6 +2661,7 @@ asmlinkage void vmx_vmexit_handler(struc case EXIT_REASON_ACCESS_GDTR_OR_IDTR: case EXIT_REASON_ACCESS_LDTR_OR_TR: case EXIT_REASON_VMX_PREEMPTION_TIMER_EXPIRED: + case EXIT_REASON_INVPCID: /* fall through */ default: exit_and_crash: diff -r c61a5ba8c972 xen/include/asm-x86/cpufeature.h --- a/xen/inc...

Hello, This series has been split into two patches, one for arm and one for x86. I figured that this was easier than doing it as a single combined patch, especially as the changes are functionally independent. x86 has been boot tested, but arm has not even been compile tested as I lack a suitable cross compiler. However, the changes are just text replacement, so I dont expect any issues. The

I''m looking into getting Xenoprof to tun in an HVM domain, since we will eventually need a profiler for HVM domains to track down areas of poor performance. (HVMs have poor performance? :) ) Being relatively new to OProfile, Xenoprof, and Xen internals, I would appreciate any pointers, tips, and comments on how to work the implementation. I see three basic areas of work. 1. Implement

The patch ''mem_event: use wait queue when ring is full'' I just sent out makes use of the waitqueue feature. There are two issues I get with the change applied: I think I got the logic right, and in my testing vcpu->pause_count drops to zero in p2m_mem_paging_resume(). But for some reason the vcpu does not make progress after the first wakeup. In my debugging there is one

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not