RE: [Xen-ia64-devel] VTi: break handling

To:	"Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-ia64-devel] VTi: break handling
From:	"Xu, Anthony" <anthony.xu@xxxxxxxxx>
Date:	Tue, 11 Apr 2006 19:59:59 +0800
Delivery-date:	Tue, 11 Apr 2006 05:00:14 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id:	Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post:	<mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcZdXtWycl4kxJzgSDWlZmwdc08zqwAADHdQ
Thread-topic:	[Xen-ia64-devel] VTi: break handling

>> It was used for debug.
>> Break 0, its opcode is 0,
>> Usually break 0 is not used by linux kernel and application.
>> When break 0 is executed, it usually means some thing wrong.
>Sure, but if an application does break 0, it locks up Xen!
>Maybe we should add a check.
>
Normal application will not use break 0, right?
Yes, we can add VTI-DEBUG macro for this.

Thanks,
Anthony

>Tristan.

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

WARNING - OLD ARCHIVES

xen-ia64-devel

RE: [Xen-ia64-devel] VTi: break handling