From: Brice Goglin <brice@myri.com>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>, Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: AMD 8131 MSI quirk called too late, bus_flags not inherited ?
Date: Sun, 21 May 2006 15:24:07 +0200 [thread overview]
Message-ID: <447069F7.1010407@myri.com> (raw)
In-Reply-To: <20060521131025.GR30211@mellanox.co.il>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Michael S. Tsirkin wrote:
>> @@ -925,8 +926,9 @@
>> if (dev->no_msi)
>> return status;
>>
>> - if (dev->bus->bus_flags & PCI_BUS_FLAGS_NO_MSI)
>> - return -EINVAL;
>> + for (bus = dev->bus; bus; bus = bus->parent)
>> + if (bus->bus_flags & PCI_BUS_FLAGS_NO_MSI)
>> + return -EINVAL;
>>
>> temp = dev->irq;
>>
>
> It seems we must add this loop to pci_enable_msix as well.
>
Right, thanks. Greg, what do you think of putting the attached patch in
2.6.17 ?
By the way, do we need to check dev->no_msi in pci_enable_msix() too ?
For 2.6.18, I don't know what's the best. We could drop the fact that
bus flags should be inherited and keep looking at parent busses. It
might be good to add a pci_check_flag_in_parent_busses(dev, flag) to
provide a generic way to do my for loop.
thanks,
Brice
Signed-off-by: Brice Goglin <brice@myri.com>
[-- Attachment #2: look_at_parent_busses_flags.patch --]
[-- Type: text/x-patch, Size: 1124 bytes --]
Index: linux-mm/drivers/pci/msi.c
===================================================================
--- linux-mm.orig/drivers/pci/msi.c 2006-05-21 15:12:04.000000000 +0200
+++ linux-mm/drivers/pci/msi.c 2006-05-21 15:15:34.000000000 +0200
@@ -916,6 +916,7 @@
**/
int pci_enable_msi(struct pci_dev* dev)
{
+ struct pci_bus *bus;
int pos, temp, status = -EINVAL;
u16 control;
@@ -925,8 +926,9 @@
if (dev->no_msi)
return status;
- if (dev->bus->bus_flags & PCI_BUS_FLAGS_NO_MSI)
- return -EINVAL;
+ for (bus = dev->bus; bus; bus = bus->parent)
+ if (bus->bus_flags & PCI_BUS_FLAGS_NO_MSI)
+ return -EINVAL;
temp = dev->irq;
@@ -1162,6 +1164,7 @@
**/
int pci_enable_msix(struct pci_dev* dev, struct msix_entry *entries, int nvec)
{
+ struct pci_bus *bus;
int status, pos, nr_entries, free_vectors;
int i, j, temp;
u16 control;
@@ -1170,6 +1173,10 @@
if (!pci_msi_enable || !dev || !entries)
return -EINVAL;
+ for (bus = dev->bus; bus; bus = bus->parent)
+ if (bus->bus_flags & PCI_BUS_FLAGS_NO_MSI)
+ return -EINVAL;
+
status = msi_init();
if (status < 0)
return status;
next prev parent reply other threads:[~2006-05-21 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 21:11 AMD 8131 MSI quirk called too late, bus_flags not inherited ? Brice Goglin
2006-05-18 15:54 ` Greg KH
2006-05-21 10:16 ` Michael S. Tsirkin
2006-05-21 10:58 ` Brice Goglin
2006-05-21 12:17 ` Michael S. Tsirkin
2006-05-21 12:31 ` Brice Goglin
2006-05-21 13:10 ` Michael S. Tsirkin
2006-05-21 13:24 ` Brice Goglin [this message]
2006-05-23 4:19 ` Greg KH
2006-05-23 7:05 ` Brice Goglin
2006-05-24 16:59 ` Michael S. Tsirkin
2006-05-24 17:05 ` Rajesh Shah
2006-05-21 13:29 ` Michael S. Tsirkin
[not found] <fa.WOQy7TVxeMkzxI+BbQP2Wqi34A0@ifi.uio.no>
[not found] ` <fa.7RUPmW8q906KfAmuRItEvwbAUvg@ifi.uio.no>
2006-05-21 19:19 ` Dave Olson
[not found] <fa.qrx8XYAhsFvMnCfipnnEkuNPFSA@ifi.uio.no>
[not found] ` <fa.hVNDQ4A/sPeiQKqlsb6JDQFEpLE@ifi.uio.no>
2006-05-23 7:32 ` Dave Olson
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=447069F7.1010407@myri.com \
--to=brice@myri.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@mellanox.co.il \
/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