Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754378AbYFDRxz (ORCPT ); Wed, 4 Jun 2008 13:53:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761891AbYFDRxk (ORCPT ); Wed, 4 Jun 2008 13:53:40 -0400 Received: from kirk.serum.com.pl ([213.77.9.205]:64316 "EHLO serum.com.pl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1761869AbYFDRxj (ORCPT ); Wed, 4 Jun 2008 13:53:39 -0400 Date: Wed, 4 Jun 2008 18:53:05 +0100 (BST) From: "Maciej W. Rozycki" To: Thomas Gleixner cc: Stefan Assmann , "Eric W. Biederman" , Olaf Dabrunz , Ingo Molnar , "H. Peter Anvin" , Jon Masters , linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/7] Boot IRQ quirks and rerouting In-Reply-To: Message-ID: References: <12124107071847-git-send-email-od@suse.de> <4846651F.4070802@suse.de> <48467DA7.9030309@suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 939 Lines: 24 On Wed, 4 Jun 2008, Thomas Gleixner wrote: > There is no way to take care of an unwanted interrupt when there is no > handler which knows to deal with the device. Of course. > The problem case is mostly preempt-rt, where we receive the interrupt, > mask it and wake up the handler thread. We can not leave it unmasked > for obvious reasons. Hmm, I can see what the problem is now -- you can mask the input of the primary I/O APIC in this case (with no side effects), making other sources at that line suffer, but at least you get away. Anyway, my other questions remain open. How is the INTx message actually delivered to the ICH? And why is the command line option needed? Maciej -- 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/