From owner-freebsd-current@FreeBSD.ORG  Wed Dec  7 07:21:07 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 808E416A41F;
	Wed,  7 Dec 2005 07:21:07 +0000 (GMT)
	(envelope-from darren.pilgrim@bitfreak.org)
Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3B91C43D45;
	Wed,  7 Dec 2005 07:21:07 +0000 (GMT)
	(envelope-from darren.pilgrim@bitfreak.org)
Received: from smiley (mail.bitfreak.org [65.75.198.146])
	by mail.bitfreak.org (Postfix) with ESMTP id 4D9C419F2C;
	Tue,  6 Dec 2005 23:21:06 -0800 (PST)
From: "Darren Pilgrim" <darren.pilgrim@bitfreak.org>
To: "'John Baldwin'" <jhb@FreeBSD.org>
Date: Tue, 6 Dec 2005 23:20:59 -0800
Message-ID: <018e01c5fafe$c9154a20$642a15ac@smiley>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: 
Importance: Normal
Cc: current@FreeBSD.org
Subject: RE: can someone explain...[ PCI interrupts] 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Wed, 07 Dec 2005 07:21:07 -0000

From: John Baldwin
>=20
> The reason [for masking interrupts] is that PCI interrupts are level
> triggered, so they won't "shut up" until the ISR has run and pacified
> the PCI device.

But PCI interrupts can be programmed either level- or edge-triggered, so
wouldn't programming to edge-triggered interrupts solve the "they won't =
shut
up" issue?