linux-kernel - Re: PCI Interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070919125023.GC3226@ff.dom.local>
Date:	Wed, 19 Sep 2007 14:50:23 +0200
From:	Jarek Poplawski <jarkao2@...pl>
To:	"Rafael J\. Wysocki" <rjw@...k.pl>
Cc:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>,
	Duncan.Perrett@...kta.com,
	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: PCI Interrupt

On Wed, Sep 19, 2007 at 02:32:12PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, 19 September 2007 12:14, Jarek Poplawski wrote:
> > On 18-09-2007 16:42, Rafael J. Wysocki wrote:
> > ...
> > > 
> > > Hm, edge-triggered interrupts cannot be shared, AFAIK.
> > > 
> > 
> > Let's agree it's only a superstition...
> > 
> > http://en.wikipedia.org/wiki/Edge_triggered_interrupt
> 
> Well, if this is an MSI (which is edge-triggered), for example, it cannot be
> shared.

I'd rather say: "which is handled like edge-triggered".

> 
> Also, you must use a level-triggered interrupt for SCI, because that has to be
> shareable.

O.K. Let's agree we differ here a bit...

Cheers,
Jarek P.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/