Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 27 Mar 2002 10:30:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 27 Mar 2002 10:30:02 -0500 Received: from netfinity.realnet.co.sz ([196.28.7.2]:3565 "HELO netfinity.realnet.co.sz") by vger.kernel.org with SMTP id ; Wed, 27 Mar 2002 10:29:50 -0500 Date: Wed, 27 Mar 2002 17:18:59 +0200 (SAST) From: Zwane Mwaikambo X-X-Sender: zwane@netfinity.realnet.co.sz To: "Maciej W. Rozycki" Cc: Dave Jones , Linux Kernel Subject: Re: [PATCH][RFC] P4/Xeon Thermal LVT support In-Reply-To: Message-ID: 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 On Wed, 27 Mar 2002, Maciej W. Rozycki wrote: > You can't use a vector that is in the range assigned to I/O APIC > interrupts (i.e. 0x31 - 0xee). Otherwise you'll get an overlap when the > vector gets assigned to an ordinary IRQ line. Also you probably want a Thanks, i'll fix that. > high-priority interrupt as the condition is serious, if not critical -- > system failures, such as bus exceptions, machine check faults, parity > errors, power failures, etc. demand a high priority service. Its really not that critical, its more informational, the interrupt handler in fact only displays a warning, by which time the hardware is already handling the condition. Thanks for the input. Zwane -- http://function.linuxpower.ca - 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/