linux-kernel - RE: [PATCH 2.6.21-rc5] MSI: read-flush MSI-X table

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]

Date:	Tue, 27 Mar 2007 08:31:09 -0700
From:	"Williams, Mitch A" <mitch.a.williams@...el.com>
To:	"Grant Grundler" <grundler@...isc-linux.org>
Cc:	<linux-pci@...ey.karlin.mff.cuni.cz>, <gregkh@...e.de>,
	<ebiederm@...ssion.com>, <linux-kernel@...r.kernel.org>,
	<akpm@...ux-foundation.org>,
	"Kok, Auke-jan H" <auke-jan.h.kok@...el.com>
Subject: RE: [PATCH 2.6.21-rc5] MSI: read-flush MSI-X table

Grant Grundler wrote: 

>Why wouldn't MSI have the same problems as MSI-X?
>

Because enabling and disabling the MSI interrupt is done through
config space, and config space writes are not posted.  So we won't
see the problem that we do with MSI-X.

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