public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <brice@myri.com>
To: Reuben Farrelly <reuben-lkml@reub.net>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: 2.6.17-mm5
Date: Sat, 01 Jul 2006 09:06:14 -0400	[thread overview]
Message-ID: <44A67346.5030705@myri.com> (raw)
In-Reply-To: <44A66B17.50008@reub.net>

Reuben Farrelly wrote:
>>
>> It oopsed here:
>>
>> static
>> int pci_msi_supported(struct pci_dev * dev)
>> {
>>     struct pci_dev *pdev;
>>
>>     if (!pci_msi_enable || !dev || dev->no_msi)
>>         return -1;
>>
>>     /* find root complex for our device */
>>     pdev = dev;
>>     while (pdev->bus && pdev->bus->self)
>>         pdev = pdev->bus->self;
>>
>>     /* check its bus flags */
>>     if (pdev->subordinate->bus_flags & PCI_BUS_FLAGS_NO_MSI)
>>         return -1;
>>
>>     return 0;
>> }
>>
>> pdev->subordinate is NULL.
>>
>
>> You may find that this gets things going again:
>>
>> --- a/drivers/pci/msi.c~a
>> +++ a/drivers/pci/msi.c
>> @@ -913,6 +913,9 @@ int pci_msi_supported(struct pci_dev * d
>>      while (pdev->bus && pdev->bus->self)
>>          pdev = pdev->bus->self;
>>  
>> +    if (!pdev->subordinate)
>> +        return -1;
>> +
>>      /* check its bus flags */
>>      if (pdev->subordinate->bus_flags & PCI_BUS_FLAGS_NO_MSI)
>>          return -1;
>> _
> Yes it does.

I was not expecting a root chipset without subordinate bus... Maybe we
should store the NO_MSI flags in the device itself instead of in its
subordinate bus (I would have to rework all my patches then). After all,
we don't inherit bus flags anymore, and I don't see why bus flags would
have been chosen initially except to help flags inheritance.
I am still convinced that checking to root chipset (bus) flags only is a
good idea since the root chipset is where MSI are translated from PCI
messages into DMA (we don't care about MSI support in the bridges
between the chipset and the devices since they only forward PCI messages).

Brice


  reply	other threads:[~2006-07-01 13:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060701175444.958D6E00608B@knarzkiste.dyndns.org>
2006-07-01 10:35 ` 2.6.17-mm5 Andrew Morton
2006-07-01 11:08   ` 2.6.17-mm5 Reuben Farrelly
2006-07-01 11:51     ` 2.6.17-mm5 Andrew Morton
2006-07-01 12:31       ` 2.6.17-mm5 Reuben Farrelly
2006-07-01 13:06         ` Brice Goglin [this message]
2006-07-01 17:00           ` 2.6.17-mm5 Greg KH
2006-07-01 18:03   ` 2.6.17-mm5 Ralf Hildebrandt
2006-07-01 18:14   ` 2.6.17-mm5 dislikes raid-1, just like mm4 Helge Hafting
2006-07-01 22:22     ` Andrew Morton
2006-07-01 22:52       ` Jeff Garzik
2006-07-01 22:58         ` Andrew Morton
2006-07-02  4:43       ` Reuben Farrelly
2006-07-02  6:09         ` Andrew Morton
2006-07-02  5:13       ` Reuben Farrelly
2006-07-02 13:53         ` James Bottomley
2006-07-02 14:28           ` Grant Wilson
2006-07-02 15:06             ` James Bottomley
2006-07-02 15:43               ` Grant Wilson
2006-07-02 19:07                 ` Helge Hafting
2006-07-03  6:52                   ` Reuben Farrelly
2006-07-02  3:51     ` Tejun Heo
     [not found]   ` <20060701142419.GB28750@tlg.swandive.local>
2006-07-01 21:30     ` 2.6.17-mm5 Andrew Morton
2006-07-01 22:26       ` 2.6.17-mm5 James Bottomley
2006-07-01 22:32         ` 2.6.17-mm5 Neil Brown
2006-07-01 22:56           ` 2.6.17-mm5 Jeff Garzik
2006-07-02  0:10             ` 2.6.17-mm5 James Bottomley
2006-07-01 22:29       ` More RAID / SATA / barrier problems [ Re: 2.6.17-mm5 ] Neil Brown
2006-07-01 22:54       ` 2.6.17-mm5 Jeff Garzik
2006-07-27 21:02       ` 2.6.17-mm5 Ming Zhang
2006-07-02 10:03   ` 2.6.17-mm5 Andy Whitcroft
2006-07-02 10:14     ` 2.6.17-mm5 Andrew Morton
2006-07-02 10:40       ` 2.6.17-mm5 Andy Whitcroft
2006-07-02 11:14         ` 2.6.17-mm5 Andrew Morton
2006-07-03  0:47   ` 2.6.17-mm5 Theodore Tso
2006-07-03  7:32   ` 2.6.17-mm5 Heiko Carstens
2006-07-02 23:27 2.6.17-mm5 Martin J. Bligh
2006-07-02 23:41 ` 2.6.17-mm5 Andrew Morton
2006-07-03  8:23   ` 2.6.17-mm5 Andy Whitcroft
2006-07-03 14:19     ` 2.6.17-mm5 Andy Whitcroft

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=44A67346.5030705@myri.com \
    --to=brice@myri.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reuben-lkml@reub.net \
    /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