search for: trap_debug

...set by doing following operation: regs->eflag |= X86_EFLAGS_TF And return the control from sh_page_fault function by saying "return EFAULT_FIXED". My understanding is that with this flag set when guest completes the execution of the next instruction, it traps to Xen with exit reason TRAP_debug and do_debug handler should be invoked inside x86/traps.c. From there, again I set X86_EFLAGS_TF flag to get guest trapped for next instruction and so on. When i want it to be end I will set X86_EFLAGS_RF flag. However, when I perform above-mentioned procedure I get to see a message "Trace/br...

...ecent batch of security updates I noticed that the obvious backport of the related patch caused an HVM guest to be crashed as soon as a user inside that guest tried to ptrace a child process. While talking to Jan, I realized that in 4.2 the inject exception code subtly changed in a way that treats TRAP_debug as a HW event (that is triggered by no opcode) while before it was always treated as SW event. I believe Debian might be affected by the same as you also have a 4.1.x version in some stable, so I thought I share the backport I did. Jan was suggesting a slightly different coding which should do the...

...y I''ll multiplex it down to the guest, but I''m having issues. Right now, I''m enabling X86_EFLAGS_TF in vmx_intr_assist, just like where MTF is enabled if desired. It''s cleared at the start of vmx_exit_handler (if required). I''m catching single step from TRAP_debug, but when I disable stepping the guest usually seems to hang. It''s not completely frozen, because if I turn single stepping back on I see more events, and the instruction pointer is moving. I''m mainly running into problems with interrupts (I believe). I think during a context swi...

Hi, Attached patch implements the VMCB cleanbits SVM feature. Upcoming AMD CPUs introduce them and they are basically hints for the CPU which vmcb values can be re-used from the previous VMRUN instruction. Each bit represents a certain set of fields in the VMCB. Setting a bit tells the cpu it can re-use the cached value from the previous VMRUN. Clearing a bit tells the cpu to reload the values

This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP), INTn instruction emulation. Introduce new function vmx_inject_sw_exception() which deliver the software excetion, software interrupt and privileged software exception. Split hardware exception as a seperate function(old function vmx_inject_hw_exception()). Also Passed down intruction length

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),

...not deliverd here either. + * The caller of this function should set correct instruction + * length. + */ void vmx_inject_hw_exception(int trap, int error_code) { unsigned long intr_info; @@ -1365,7 +1378,6 @@ void vmx_inject_hw_exception(int trap, i switch ( trap ) { case TRAP_debug: - type = X86_EVENTTYPE_SW_EXCEPTION; if ( guest_cpu_user_regs()->eflags & X86_EFLAGS_TF ) { __restore_debug_registers(curr); @@ -1383,16 +1395,14 @@ void vmx_inject_hw_exception(int trap, i return; } - type = X86_EVENTTYPE...

Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 _______________________________________________ Xen-devel mailing list

Clearing out my local queue of changes before applying other''s.

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.