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

[Xen-devel] noirqdebug_setup() in arch/i386/kernel/setup-xen.c

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] noirqdebug_setup() in arch/i386/kernel/setup-xen.c
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 07 Apr 2006 11:00:15 +0200
Delivery-date: Fri, 07 Apr 2006 02:00:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Can anyone explain why i386 calls noirqdebug_setup() unconditionally, while 
x86-64 doesn't? I believe this is the reason
why we have been seeing spurious interrupt reports only on 64-bits so far.

What was this supposed to suppress originally? Is this still applicable? It 
would seem to me that hiding problems in
this area is rather undesirable...

Thanks, Jan

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

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