linux-kernel - Re: [PATCH 5/7] I/OAT: Add support for MSI and MSI-X

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: <1a297b360707201432q3dc976b3x214c2916ca235b6f@mail.gmail.com>
Date:	Sat, 21 Jul 2007 01:32:36 +0400
From:	"Manu Abraham" <abraham.manu@...il.com>
To:	"Roland Dreier" <rdreier@...co.com>
Cc:	"Leech, Christopher" <christopher.leech@...el.com>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>,
	"Nelson, Shannon" <shannon.nelson@...el.com>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	davem@...emloft.net, jeff@...zik.org,
	"Williams, Dan J" <dan.j.williams@...el.com>
Subject: Re: [PATCH 5/7] I/OAT: Add support for MSI and MSI-X

On 7/21/07, Roland Dreier <rdreier@...co.com> wrote:
>  > This driver supports some chipsets that do MSI, and some that do MSI-X,
>  > but none that can do both.
>
> Thanks, that's the simple answer I was hoping for.  Obviously if some
> chipsets only do MSI then you need the MSI code in addition to the
> MSI-X code.

In a case where you have a device that which supports MSI-X (multiple
interrupts) but the device in default is in MSI mode, ie some
configuration change is needed on the device. In such a case, how
would one handle between MSI-X and MSI ?

ie the device initially doesn't support MSI-X
-
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/