Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264227AbTEGU74 (ORCPT ); Wed, 7 May 2003 16:59:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264231AbTEGU74 (ORCPT ); Wed, 7 May 2003 16:59:56 -0400 Received: from ns.suse.de ([213.95.15.193]:9486 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S264227AbTEGU7z (ORCPT ); Wed, 7 May 2003 16:59:55 -0400 To: Will Dinkel Cc: linux-kernel@vger.kernel.org Subject: Re: x86_64 interrupts handled by CPU0 only References: <1052326953.22518.184.camel@zappa.suse.lists.linux.kernel> From: Andi Kleen Date: 07 May 2003 23:12:27 +0200 In-Reply-To: <1052326953.22518.184.camel@zappa.suse.lists.linux.kernel> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 482 Lines: 9 Will Dinkel writes: > Are all interrupts supposed to be handled by CPU0 on x86_64, or is > something amiss? I'm getting the following on Mandrake Corporate Server > 2.1: It's by design. You need irqbalanced. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/