linux-kernel - Re: [PATCH] Disable INTx when enabling MSI in forcedeth

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: <86802c440611212336n3a66a557mdf78ef0b6eac165a@mail.gmail.com>
Date:	Tue, 21 Nov 2006 23:36:46 -0800
From:	"Yinghai Lu" <yinghai.lu@....com>
To:	"Jeff Garzik" <jeff@...zik.org>
Cc:	"Linus Torvalds" <torvalds@...l.org>,
	"Daniel Barkalow" <barkalow@...ervon.org>,
	linux-kernel@...r.kernel.org, "David Miller" <davem@...emloft.net>,
	"Roland Dreier" <rdreier@...co.com>,
	"Ayaz Abdulla" <aabdulla@...dia.com>
Subject: Re: [PATCH] Disable INTx when enabling MSI in forcedeth

On 11/21/06, Jeff Garzik <jeff@...zik.org> wrote:
> I agree.  And it's just a simple matter of remove the PCI-Express
> brackets AFAICS, like in the attached patch (untested).

How about if the ioapic is not inited for that card?

For example, I didn't initialize irq routing/ioapci for nvidia LAN.

YH
-
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/