WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Trap flags, debug and emulation - xen 4.1.1

To: Balbir Singh <bsingharora@xxxxxxxxx>
Subject: Re: [Xen-devel] Trap flags, debug and emulation - xen 4.1.1
From: Tim Deegan <tim@xxxxxxx>
Date: Tue, 11 Oct 2011 09:26:18 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 11 Oct 2011 01:26:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAKTCnzkyYASOH_gaf+4pQoGqM4q=1r=mfLHcoP-5oy59yyHbXw@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAKTCnzkyYASOH_gaf+4pQoGqM4q=1r=mfLHcoP-5oy59yyHbXw@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
Hi, 

At 08:39 +0530 on 11 Oct (1318322368), Balbir Singh wrote:
>  I am doing something very similar. I do get the fault and I can set
>  the trap, but I don't see any form of single stepping take place as I
>  do not get the TRAP_debug exception back. My exception_bitmap has
>  TRAP_no_device, TRAP_page_fault, TRAP_debug and TRAP_int3 set.
> 
>  I've tried debugging the issue with xentrace and printks, but sadly I
>  could not track down the issue. The CPU does have
>  cpu_has_monitor_trap_flag set to true.
> 
>  Could anyone give me clues on how to track down why I did not get a
>  TRAP_debug exception via a VMEXIT?

It sounds like you're doing the right thing - just a question of looking
for the bug. :)  I would try checking for the TF flag as close as
possible to the vmenter (maybe even in the assembly - you could call out
to a special C function if it's set), and for the debug vmexit right at the
top of the vmexit handler to make sure that some other clever debugging
code isn't consuming it.   Probably also worth double-chjecking that
nothing else ois overwriting the exception bitmap before the vmenter. 

Cheers,

Tim.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>