From: Don Dutile <ddutile@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: James Paradis <jparadis@redhat.com>,
Prarit Bhargava <prarit@redhat.com>,
linux-pci@vger.kernel.org, mstowe@redhat.com,
matthew wilcox <matthew.wilcox@linux.intel.com>,
jbarnes@virtuousgeek.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: [PATCH] pci: Workaround Stratus broken PCIE hierarchy
Date: Fri, 11 Nov 2011 15:35:32 -0500 [thread overview]
Message-ID: <4EBD8714.30401@redhat.com> (raw)
In-Reply-To: <CAErSpo5eZ=4yqnMFpFjTOqGvK6p4mOmsppJbodeGe+vkjfKdbw@mail.gmail.com>
On 11/11/2011 03:29 PM, Bjorn Helgaas wrote:
> On Fri, Nov 11, 2011 at 12:13 PM, Don Dutile<ddutile@redhat.com> wrote:
>> On 11/11/2011 12:41 PM, James Paradis wrote:
>>>
>>> Hmmm... would it be better to do this as a quirk or as a boot
>>> parameter? I've heard reports that other systems may be running
>>
>> Hearsay? if you have definite cases, then please share them,
>> so folks know when to flip the boot parameter on. note: it would have to be
>> an early boot param as well.
>
> It'd definitely be good to know all the specific cases.
>
> But merely sharing them so folks will know when to use the parameter
> is a broken model. We should make it work automatically, either with
> some sort of machine-dependent quirk, or (preferably) with a change to
> the generic algorithm so it can handle these "broken" topologies along
> with all the correct ones.
>
> Bjorn
In this case, doing a check that the parent is downstream PPB and the child is
downstream PPB could be done to identify the broken topology and automatically
scan dev nums > 0.
next prev parent reply other threads:[~2011-11-11 20:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 14:00 [PATCH] pci: Workaround Stratus broken PCIE hierarchy Prarit Bhargava
2011-11-10 14:31 ` Matthew Wilcox
2011-11-10 16:50 ` Don Dutile
2011-11-11 17:41 ` James Paradis
2011-11-11 19:13 ` Don Dutile
2011-11-11 20:29 ` Bjorn Helgaas
2011-11-11 20:35 ` Don Dutile [this message]
2011-11-14 14:44 ` Prarit Bhargava
2011-11-14 18:14 ` Matthew Wilcox
2011-11-14 19:50 ` Prarit Bhargava
2011-11-15 20:16 ` Matthew Wilcox
2011-11-15 15:56 ` Prarit Bhargava
2011-11-15 16:08 ` Rolf Eike Beer
2011-11-15 18:14 ` Bjorn Helgaas
2011-11-15 18:25 ` Prarit Bhargava
2011-11-15 21:08 ` James Paradis
2011-11-15 21:52 ` Myron Stowe
2011-11-15 22:14 ` James Paradis
2011-11-15 20:15 ` Matthew Wilcox
2011-11-16 16:53 ` Prarit Bhargava
2011-11-17 0:18 ` Prarit Bhargava
2011-11-15 21:53 ` James Paradis
2011-11-15 22:27 ` James Paradis
2011-11-15 23:07 ` Don Dutile
-- strict thread matches above, loose matches on Subject: below --
2012-04-25 17:56 Prarit Bhargava
2012-04-25 23:35 ` Bjorn Helgaas
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=4EBD8714.30401@redhat.com \
--to=ddutile@redhat.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jparadis@redhat.com \
--cc=linux-pci@vger.kernel.org \
--cc=matthew.wilcox@linux.intel.com \
--cc=matthew@wil.cx \
--cc=mstowe@redhat.com \
--cc=prarit@redhat.com \
/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).