Rajesh Shah writes:
> The current MSI code actually does this deliberately, not by
> accident. It's got a lot of complex code to track devices and
> vectors and make sure an enable_msi -> disable -> enable sequence
> gives a driver the same vector. It also has policies about
> reserving vectors ba
l.org; netdev@vger.kernel.org; Leonid
Grossman; Ananda Raju; Sriram Rapuru
Subject: Re: [PATCH 2.6.16.18] MSI: Proposed fix for MSI/MSI-X load
failure
On Fri, Jun 02, 2006 at 03:21:37PM -0400, Ravinandan Arakali wrote:
>
> Symptoms:
> When a driver is loaded with MSI followed by MSI-X,
On Fri, Jun 02, 2006 at 03:21:37PM -0400, Ravinandan Arakali wrote:
>
> Symptoms:
> When a driver is loaded with MSI followed by MSI-X, the load fails indicating
> that the MSI vector is still active. And vice versa.
>
> Suspected rootcause:
> This happens inspite of driver calling free_irq() fo
Hi,
This patch suggests a fix for the MSI/MSI-X load failure.
Please review the patch.
Symptoms:
When a driver is loaded with MSI followed by MSI-X, the load fails indicating
that the MSI vector is still active. And vice versa.
Suspected rootcause:
This happens inspite of driver calling free_ir
