From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@novell.com>
Subject: noirqdebug_setup() in arch/i386/kernel/setup-xen.c
Date: Fri, 07 Apr 2006 11:00:15 +0200
Message-ID: <4436463F.76F0.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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