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-ia64-devel

[Xen-ia64-devel] Strange code in ivt.S

To: Xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Strange code in ivt.S
From: tgingold@xxxxxxx
Date: Thu, 15 Feb 2007 17:39:53 +0100
Delivery-date: Thu, 15 Feb 2007 08:36:32 -0800
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
User-agent: Mutt/1.5.9i
Hi,

A few lines after ENTRY(break_fault), there is strange code (at least to me):
        movl r18=THIS_CPU(current_psr_ic_addr)
        ;;
        ld8 r18=[r18]    
        ;;
        cmp.eq p7,p0=r0,r17                     // is this a psuedo-cover?
(p7)    br.spnt.many dispatch_privop_fault

(r17 is cr.iim).

This seems buggy code related to old privify feature.
I think this creates garbage warning on the console when break 0 is
encountered in user code.

Tristan.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-ia64-devel] Strange code in ivt.S, tgingold <=