All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joerg.roedel@amd.com>
To: Antonio Quartulli <ordex@autistici.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: warn_slowpath_common in drivers/pci/search.c:44 on linux-3.4.0
Date: Tue, 29 May 2012 12:16:57 +0200	[thread overview]
Message-ID: <20120529101657.GO2604@amd.com> (raw)
In-Reply-To: <20120529085648.GA13941@ritirata.org>

On Tue, May 29, 2012 at 10:56:50AM +0200, Antonio Quartulli wrote:
> attached!
> Some days ago I tried to put some printk in the code and, as far as I can
> understand, you are right.

Hmm, looks like device 03:00.0 is a 32bit PCI device attached to device
00:1c.2 which calls itself a Root Port instead of a PCI Bridge. I am
not sure if the check in search.c is really necessary. As I see it there
are also other possible pcie_types like PCI_EXP_TYPE_PCIE_BRIDGE.
Putting Anil Keshavamurthy on Cc.

Anil, is this check in pci_find_upstream_pcie_bridge() really
necessary:

        /* PCI device should connect to a PCIe bridge */
        if (pdev->pcie_type != PCI_EXP_TYPE_PCI_BRIDGE) {
                /* Busted hardware? */
                WARN_ON_ONCE(1);
                return NULL;
        }

? In the warning that triggers for Antonio the value of pcie_type seems
to be PCI_EXP_TYPE_ROOT_PORT and from the available types I think that
PCI_EXP_TYPE_PCIE_BRIDGE is also possible.

Thanks,

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joerg.roedel@amd.com>
To: Antonio Quartulli <ordex@autistici.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	<iommu@lists.linux-foundation.org>
Subject: Re: warn_slowpath_common in drivers/pci/search.c:44 on linux-3.4.0
Date: Tue, 29 May 2012 12:16:57 +0200	[thread overview]
Message-ID: <20120529101657.GO2604@amd.com> (raw)
In-Reply-To: <20120529085648.GA13941@ritirata.org>

On Tue, May 29, 2012 at 10:56:50AM +0200, Antonio Quartulli wrote:
> attached!
> Some days ago I tried to put some printk in the code and, as far as I can
> understand, you are right.

Hmm, looks like device 03:00.0 is a 32bit PCI device attached to device
00:1c.2 which calls itself a Root Port instead of a PCI Bridge. I am
not sure if the check in search.c is really necessary. As I see it there
are also other possible pcie_types like PCI_EXP_TYPE_PCIE_BRIDGE.
Putting Anil Keshavamurthy on Cc.

Anil, is this check in pci_find_upstream_pcie_bridge() really
necessary:

        /* PCI device should connect to a PCIe bridge */
        if (pdev->pcie_type != PCI_EXP_TYPE_PCI_BRIDGE) {
                /* Busted hardware? */
                WARN_ON_ONCE(1);
                return NULL;
        }

? In the warning that triggers for Antonio the value of pcie_type seems
to be PCI_EXP_TYPE_ROOT_PORT and from the available types I think that
PCI_EXP_TYPE_PCIE_BRIDGE is also possible.

Thanks,

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


  reply	other threads:[~2012-05-29 10:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26  8:25 warn_slowpath_common in drivers/pci/search.c:44 on linux-3.4.0 Antonio Quartulli
2012-05-26 15:09 ` Bjorn Helgaas
2012-05-29  8:35   ` Joerg Roedel
2012-05-29  8:35     ` Joerg Roedel
2012-05-29  8:56     ` Antonio Quartulli
2012-05-29 10:16       ` Joerg Roedel [this message]
2012-05-29 10:16         ` Joerg Roedel
2012-05-29 16:13         ` Jiang Liu
2013-03-24 14:34           ` Antonio Quartulli
2013-12-08 14:26       ` Antonio Quartulli
     [not found]         ` <52A4819A.50501-x4xJYDvStAgysxA8WJXlww@public.gmane.org>
2013-12-09 17:25           ` Bjorn Helgaas
2013-12-09 17:25             ` Bjorn Helgaas
2013-12-09 17:36             ` Alex Williamson
2013-12-09 17:36               ` Alex Williamson

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=20120529101657.GO2604@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=bhelgaas@google.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ordex@autistici.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.