[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] hvm trapping mechanism
Hi all, I would like to ask about hvm xen implementation. As far i understood the trapping-emulating flow is that: 1. when hvm virtual machine is started vmcs is setup and a vm_exit handler is registered at: __vmwrite(HOST_RIP, (unsigned long)vmx_asm_vmexit_handler); 2. the hypercall page is defined by hypercall api and that hypercall page contains the vmexit calls. 3. when guest os issues syscall an hypercall is perfomed by the hypercall page and vmexit operation is peformed 4. the vmx_vmexit_handler(struct cpu_user_regs *regs) (vmx.c) is invoked to emulate the hypercall. I would like to ask is this flow is right? Is there somethingimportant missing? I would like to ask how the vmx_vmexit_handler is invoked - may be on hardware level or there is some other party at the flow? best regerds -- View this message in context: http://xen.1045712.n5.nabble.com/hvm-trapping-mechanism-tp5720529.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |