[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A0A4F4A.7030101@jp.fujitsu.com>
Date: Wed, 13 May 2009 13:40:42 +0900
From: Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
To: michael@...erman.id.au
CC: Matthew Wilcox <matthew@....cx>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
"David S. Miller" <davem@...emloft.net>, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix MSI-X with NIU cards
Hidetoshi Seto wrote:
> It seems that this issue was introduced by Matthew's commit:
> commit f2440d9acbe866b917b16cc0f927366341ce9215
> <quote>
> @@ -435,11 +432,12 @@ static int msix_capability_init(struct pci_dev *dev,
> entry->msi_attrib.is_msix = 1;
> entry->msi_attrib.is_64 = 1;
> entry->msi_attrib.entry_nr = j;
> - entry->msi_attrib.maskbit = 1;
> - entry->msi_attrib.masked = 1;
> entry->msi_attrib.default_irq = dev->irq;
> entry->msi_attrib.pos = pos;
> entry->mask_base = base;
> + entry->masked = readl(base + j * PCI_MSIX_ENTRY_SIZE +
> + PCI_MSIX_ENTRY_VECTOR_CTRL_OFFSET);
> + msix_mask_irq(entry, 1);
>
> list_add_tail(&entry->list, &dev->msi_list);
> }
> </quote>
>
> I'm not sure why Matthew changed it to read/write...
Sorry, I got it.
The problem is not the bit[0] for mask, but the reserved bits[31::01].
According to the Spec:
"31::01 Reserved
After reset, the state of these bits must be 0.
However, for potential future use, software must preserve the value of
these reserved bits when modifying the value of other Vector Control bits.
If software modifies the value of these reserved bits, the result is
undefined."
I'll post a revised fix soon.
Thanks,
H.Seto
--
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/
Powered by blists - more mailing lists