From: Michael Ellerman <michael@ellerman.id.au>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
"David S. Miller" <davem@davemloft.net>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix MSI-X with NIU cards
Date: Mon, 11 May 2009 11:21:51 +1000 [thread overview]
Message-ID: <1242004911.7767.26.camel@concordia> (raw)
In-Reply-To: <20090508131333.GV8112@parisc-linux.org>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
On Fri, 2009-05-08 at 07:13 -0600, Matthew Wilcox wrote:
> The NIU device refuses to allow accesses to MSI-X registers before MSI-X
> is enabled. This patch fixes the problem by moving the read of the mask
> register to after MSI-X is enabled.
>
> Reported-by: David S. Miller <davem@davemloft.net>
> Tested-by: David S. Miller <davem@davemloft.net>
> Reviewed-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
>
> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
> index 6f2e629..3627732 100644
> --- a/drivers/pci/msi.c
> +++ b/drivers/pci/msi.c
> @@ -455,8 +455,6 @@ static int msix_capability_init(struct pci_dev *dev,
> 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);
158 static void msix_mask_irq(struct msi_desc *desc, u32 flag)
159 {
160 u32 mask_bits = desc->masked;
...
165 writel(mask_bits, desc->mask_base + offset);
So I guess this device is just silently ignoring that write?
And aren't we violating the spec by writing 0x1 into the device there
(assuming desc->masked is 0x0 from the kzalloc), ie. we're supposed to
read and write back the reserved bits unchanged. (§ 6.8.2.9?)
> @@ -493,6 +491,12 @@ static int msix_capability_init(struct pci_dev *dev,
> msix_set_enable(dev, 1);
> dev->msix_enabled = 1;
Are we safe if we take an interrupt here?
> + list_for_each_entry(entry, &dev->msi_list, list) {
> + int vector = entry->msi_attrib.entry_nr;
> + entry->masked = readl(base + vector * PCI_MSIX_ENTRY_SIZE +
> + PCI_MSIX_ENTRY_VECTOR_CTRL_OFFSET);
> + }
> +
> return 0;
> }
>
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-11 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 13:13 [PATCH] Fix MSI-X with NIU cards Matthew Wilcox
2009-05-11 1:21 ` Michael Ellerman [this message]
2009-05-11 5:36 ` David Miller
2009-05-11 14:30 ` Michael Ellerman
2009-05-11 23:40 ` David Miller
2009-05-11 23:59 ` Jesse Barnes
2009-05-12 2:21 ` Michael Ellerman
2009-05-13 10:07 ` Matthew Wilcox
2009-05-13 4:06 ` Hidetoshi Seto
2009-05-13 4:40 ` Hidetoshi Seto
2009-05-13 4:49 ` Michael Ellerman
2009-05-13 4:10 ` [PATCH] PCI MSI: Yet another fix for " Hidetoshi Seto
2009-05-13 5:13 ` David Miller
2009-05-13 4:54 ` [PATCH] PCI MSI: Yet another fix for MSI-X with NIU cards, v2 Hidetoshi Seto
2009-05-13 5:06 ` Hidetoshi Seto
2009-05-13 6:31 ` Michael Ellerman
2009-05-13 18:43 ` Matthew Wilcox
2009-05-14 6:22 ` Hidetoshi Seto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1242004911.7767.26.camel@concordia \
--to=michael@ellerman.id.au \
--cc=davem@davemloft.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox