From owner-freebsd-current@FreeBSD.ORG  Sun May 11 19:20:42 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AB79F37B401
	for <current@freebsd.org>; Sun, 11 May 2003 19:20:42 -0700 (PDT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7FD1E43FCB
	for <current@freebsd.org>; Sun, 11 May 2003 19:20:41 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from curly.cs.duke.edu (curly.cs.duke.edu [152.3.140.76])
	by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h4C2KdMS022251
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 11 May 2003 22:20:39 -0400 (EDT)
Received: (from gallatin@localhost)
	by curly.cs.duke.edu (8.12.9/8.12.9/Submit) id h4C2KdCL006582;
	Sun, 11 May 2003 22:20:39 -0400 (EDT)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16063.1270.712211.263308@curly.cs.duke.edu>
Date: Sun, 11 May 2003 22:20:38 -0400 (EDT)
To: Paul Richards <paul@freebsd-services.com>
In-Reply-To: <1052703871.4921.146.camel@cf.freebsd-services.com>
References: <22333.1052574519@critter.freebsd.dk>
	<20030511.134504.85393710.imp@bsdimp.com>
	<1052684139.4921.3.camel@cf.freebsd-services.com>
	<20030511.143231.133432780.imp@bsdimp.com>
	<1052692357.4921.128.camel@cf.freebsd-services.com>
	<16062.59918.302092.929640@curly.cs.duke.edu>
	<1052703871.4921.146.camel@cf.freebsd-services.com>
X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
cc: current@freebsd.org
Subject: Re: Interrupt latency problems
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2003 02:20:43 -0000


Paul Richards writes:
 > 
 > As a further datapoint to my last email:
 > 
 >    20  ??  WL     5:16.38  (irq9: fxp0 acpi0)
 > 
 > I'll see if I can shift the interrupts around in the bios but I don't
 > think I can since fxp is onboard.

I think you might be able to reserve IRQ 9 for some legacy device or
something in the BIOS.

 > Perhaps acpi doesn't do anything to check whether the interrupt belongs
 > to it or not and so when an fxp interrupt arrives the acpi handler gets
 > called.

That's a good theory.  I think you might have something there.


Drew