From: David Daney <ddaney@caviumnetworks.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "David Daney" <ddaney.cavm@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-api@vger.kernel.org,
"Sean O. Stalley" <sean.stalley@intel.com>,
"Rajat Jain" <rajatxjain@gmail.com>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
"David Daney" <david.daney@cavium.com>
Subject: Re: [PATCH v4 3/5] PCI: Handle IORESOURCE_PCI_FIXED when sizing and assigning resources.
Date: Fri, 2 Oct 2015 16:38:52 -0700 [thread overview]
Message-ID: <560F158C.4040303@caviumnetworks.com> (raw)
In-Reply-To: <CAE9FiQWnE3ucbjPKuXm5qhTGx7bYOBqnNoSNOMaJa_tEf3Z4=Q@mail.gmail.com>
On 10/02/2015 04:14 PM, Yinghai Lu wrote:
> On Fri, Oct 2, 2015 at 3:37 PM, David Daney <ddaney.cavm@gmail.com> wrote:
>> From: David Daney <david.daney@cavium.com>
>>
>> The new Enhanced Allocation (EA) capability support creates resources
>> with the IORESOURCE_PCI_FIXED set. This creates a couple of problems:
>>
>> 1) Since these resources cannot be relocated or resized, their
>> alignment is not really defined, and it is therefore not specified.
>> This causes a problem in pbus_size_mem() where resources with
>> unspecified alignment are disabled.
>>
>> 2) During resource assignment in pci_bus_assign_resources(),
>> IORESOURCE_PCI_FIXED resources are not given a parent. This, in
>> turn, causes pci_enable_resources() to fail with a "not claimed"
>> error.
>>
>> So, in pbus_size_mem() skip IORESOURCE_PCI_FIXED resources, instead of
>> disabling them.
>>
>> In __pci_bus_assign_resources(), for IORESOURCE_PCI_FIXED resources,
>> try to request the resource from a parent bus.
>
> Can you check if
>
> https://patchwork.kernel.org/patch/7304971/
> [v6,05/53] PCI: Don't release fixed resource for realloc
This one isn't relevant as the problem is seen when we are acquiring
resources, not releasing them.
>
> https://patchwork.kernel.org/patch/7304371/
> [v6,06/53] PCI: Claim fixed resource during remove/rescan path
This one is interesting, but I don't think it will work.
pci_claim_resource() calls pci_find_parent_resource(), which will fail
in important use cases.
It is perfectly legal for a bridge provisioned by EA to not specify any
resources. In this case we must walk up the bus tree until we find
something that contains the device resource, and can thus be a parent.
That is a big part of what my patch is doing.
As for the merits of assigning fixed resources from the FINAL fixup,
rather than in __pci_bus_assign_resources(), I am unsure.
Thanks,
David Daney
>
> address the the problem that you met?
>
> Yinghai
>
next prev parent reply other threads:[~2015-10-02 23:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 22:37 [PATCH v4 0/5] PCI: Add support for PCI Enhanced Allocation "BARs" David Daney
2015-10-02 22:37 ` [PATCH v4 1/5] PCI: Add Enhanced Allocation register entries David Daney
2015-10-02 22:37 ` [PATCH v4 2/5] PCI: Add support for Enhanced Allocation devices David Daney
2015-10-02 22:37 ` [PATCH v4 3/5] PCI: Handle IORESOURCE_PCI_FIXED when sizing and assigning resources David Daney
2015-10-02 23:14 ` Yinghai Lu
2015-10-02 23:38 ` David Daney [this message]
2015-10-03 3:00 ` Yinghai Lu
2015-10-05 22:44 ` Sean O. Stalley
2015-10-05 22:23 ` Sean O. Stalley
2015-10-06 20:58 ` David Daney
2015-10-02 22:37 ` [PATCH v4 4/5] PCI: Handle Enhanced Allocation (EA) capability for SRIOV devices David Daney
2015-10-02 22:37 ` [PATCH v4 5/5] PCI: Handle Enhanced Allocation (EA) capability for bridges David Daney
2015-10-05 22:54 ` Sean O. Stalley
2015-10-05 23:01 ` David Daney
2015-10-02 23:47 ` [PATCH v4 0/5] PCI: Add support for PCI Enhanced Allocation "BARs" Sean O. Stalley
2015-10-03 3:16 ` Yinghai Lu
2015-10-05 16:49 ` David Daney
2015-10-05 23:05 ` Sean O. Stalley
2015-10-06 1:17 ` David Daney
2015-10-06 15:47 ` Sean O. Stalley
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=560F158C.4040303@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=bhelgaas@google.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rajatxjain@gmail.com \
--cc=sean.stalley@intel.com \
--cc=yinghai@kernel.org \
--cc=zajec5@gmail.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