search for: xenoprof_log_ev

...t; Please apply to xen-unstable.hg. hvm_xenoprofile_2.patch - The second patch adds the actual xenoprofile fixes for SVM: 1) hvm function (svm_oprofile_get_eip()) This new hvm table function is called from the op_module_athlon.c code, and returns the proper eip and "mode" for use in the xenoprof_log_event() function. 2) The vmexit handler code now checks the exitcode and if an NMI was intercepted, then prior to the stgi(), a flag (VGCF_hvm_guest_nmi) is set in the v->arch.guest_context.flags field. The VGCF_hvm_guest_nmi bit is checked during NMI processing via the hvm function callback....

...determine proper rip/eip and mode. hvm_xenoprofile_2.patch - The second patch adds the actual xenoprofile fixes for SVM: 1) hvm function (svm_oprofile_get_eip()) This new hvm table function is called from the op_module_athlon.c code, and returns the proper eip and "mode" for use in the xenoprof_log_event() function. 2) The vmexit handler code now checks the exitcode and if an NMI was intercepted, then prior to the stgi(), a flag (VGCF_hvm_guest_nmi) is set in the v->arch.guest_context.flags field. The VGCF_hvm_guest_nmi bit is checked during NMI processing via the hvm function callback....

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of