From: Brice Goglin <brice@myri.com>
To: Michael Chan <mchan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH][BNX2]: Disable MSI on 5706 if AMD 8132 bridge is present
Date: Sat, 30 Sep 2006 12:13:34 +0200 [thread overview]
Message-ID: <451E434E.5040500@myri.com> (raw)
In-Reply-To: <1159564053.3741.19.camel@rh4>
Michael Chan a écrit :
> AMD believes this incompatibility is unique to the 5706, and
> prefers to locally disable MSI rather than globally disabling it
> using pci_msi_quirk.
>
FYI, pci_msi_quirk is the extreme solution, there is something in the
middle :) It is possible to disable MSI for only devices that are behind
this bridge (by setting the NO_MSI flag in its bus flag). We just merged
a couple patchs related to this NO_MSI flag and pci_msi_quirk (there are
very very few cases where MSI must be disabled globally, most of the
time a subset behind a bridge is enough) so I am very glad that you
didn't use it :)
Anyway, disabling locally is better here.
> + if (CHIP_NUM(bp) == CHIP_NUM_5706 && disable_msi == 0) {
> + struct pci_dev *amd_8132 = NULL;
> +
> + while ((amd_8132 = pci_get_device(PCI_VENDOR_ID_AMD,
> + PCI_DEVICE_ID_AMD_8132_BRIDGE,
> + amd_8132))) {
>
What if the machine has such a bridge and board, but the board is not
actually located somewhere behind the bridge? I would rather walk the
PCI hierarchy from the board to the top and check whether we find a
AMD8132. Probably something like:
struct pci_dev * bridge = <the bnx2 pci_dev>;
while (bridge->bus && bridge->bus->self)
bridge = bridge->bus->self;
if (bridge->vendor == PCI_VENDOR_ID_AMD
&& bridge->device == PCI_VENDOR_ID_AMD_8132_BRIDGE)
<do your stuff to disable MSI on your board>
Brice
next prev parent reply other threads:[~2006-09-30 10:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 21:07 [PATCH][BNX2]: Disable MSI on 5706 if AMD 8132 bridge is present Michael Chan
2006-09-29 21:28 ` Jeff Garzik
2006-09-29 21:39 ` Michael Chan
2006-09-29 22:49 ` David Miller
2006-09-29 23:00 ` Jeff Garzik
2006-09-29 23:08 ` David Miller
2006-09-29 23:15 ` Jeff Garzik
2006-09-29 23:27 ` Michael Chan
2006-09-29 23:29 ` David Miller
2006-09-30 0:38 ` Jeff Garzik
2006-09-30 1:22 ` David Miller
2006-09-29 23:46 ` Rick Jones
2006-09-30 0:16 ` Roland Dreier
2006-09-30 0:07 ` David Miller
2006-09-30 10:13 ` Brice Goglin [this message]
2006-09-30 18:09 ` Michael Chan
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=451E434E.5040500@myri.com \
--to=brice@myri.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).