From: Yinghai Lu <yinghai@kernel.org>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio
Date: Thu, 25 Sep 2014 11:24:01 -0700 [thread overview]
Message-ID: <CAE9FiQX-ZDTOa6fKvHry8XCqPKSLZt8QKYm97cZXJsRNLB9yRg@mail.gmail.com> (raw)
In-Reply-To: <54245C94.2020708@canonical.com>
On Thu, Sep 25, 2014 at 11:19 AM, Joseph Salisbury
<joseph.salisbury@canonical.com> wrote:
> On 09/17/2014 03:46 AM, Yinghai Lu wrote:
>> On Tue, Sep 16, 2014 at 3:27 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>>> On Tue, Sep 16, 2014 at 1:21 PM, Joseph Salisbury
>>> <joseph.salisbury@canonical.com> wrote:
>>>> A new bug[0] was opened due to enabling PCI_REALLOC_ENABLE_AUTO, which
>>>> is similar to the original bug[1] we discussed.
>>>>
>>>> Just wondering if there have been any additional ideas on realloc since
>>>> this was last discussed?
>>>>
>>>> [0] http://pad.lv/1363313
>>> So the resource realloc do work as expected. but LSI firmware has some
>>> problem again?
>>>
>>> We may need to add command after the reset the bridge resource.
>> Can you try attached patch?
>>
>> Thanks
>>
>> Yinghai
> Sorry, this message was marked as SPAM for some reason. Do you still
> want this patch tested?
Yes, Please.
We need special handling for LSI devices.
Thanks
Yinghai
next prev parent reply other threads:[~2014-09-25 18:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:54 [PATCH 0/2] PCI: Don't enable realloc automatically when above 4g 64bit mmio is not supported Yinghai Lu
2013-12-08 23:54 ` [PATCH 1/2] PCI: pcibus address to resource converting take bus instead of dev Yinghai Lu
2013-12-09 17:52 ` Bjorn Helgaas
2013-12-09 19:21 ` Yinghai Lu
2013-12-09 20:03 ` Yinghai Lu
2013-12-09 20:43 ` Greg KH
2013-12-09 20:47 ` Yinghai Lu
2013-12-09 21:06 ` Bjorn Helgaas
2013-12-08 23:54 ` [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio Yinghai Lu
2013-12-09 17:54 ` Bjorn Helgaas
2013-12-09 19:20 ` Yinghai Lu
2013-12-09 19:42 ` Bjorn Helgaas
2013-12-09 20:10 ` Yinghai Lu
2013-12-09 20:20 ` Bjorn Helgaas
2013-12-09 20:44 ` Yinghai Lu
2013-12-09 21:05 ` Bjorn Helgaas
2013-12-11 19:19 ` Joseph Salisbury
2013-12-11 19:55 ` Yinghai Lu
2014-01-08 16:38 ` Joseph Salisbury
2014-01-10 16:19 ` Joseph Salisbury
2014-01-10 17:13 ` Yinghai Lu
2014-01-10 21:54 ` Joseph Salisbury
2014-01-10 23:12 ` Yinghai Lu
2014-09-16 20:21 ` Joseph Salisbury
2014-09-16 22:27 ` Yinghai Lu
2014-09-17 7:46 ` Yinghai Lu
2014-09-24 23:48 ` Bjorn Helgaas
2014-09-25 18:19 ` Joseph Salisbury
2014-09-25 18:24 ` Yinghai Lu [this message]
2014-09-25 15:49 ` Joseph Salisbury
2014-09-25 16:04 ` Bjorn Helgaas
2014-09-25 18:04 ` Joseph Salisbury
2014-09-25 18:23 ` Yinghai Lu
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=CAE9FiQX-ZDTOa6fKvHry8XCqPKSLZt8QKYm97cZXJsRNLB9yRg@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stable@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).