From: Ram Pai <linuxram@us.ibm.com>
To: jbarnes@virtuousgeek.org
Cc: torvalds@linux-foundation.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, yinghai@kernel.org,
bhutchings@solarflare.com, socketcan@hartkopp.net,
bhelgaas@google.com, linux@dominikbrodowski.net,
linuxram@us.ibm.com
Subject: [PATCH 0/5 v3] PCI: fix cardbus and sriov regressions
Date: Mon, 25 Jul 2011 13:08:37 -0700 [thread overview]
Message-ID: <1311624522-30242-1-git-send-email-linuxram@us.ibm.com> (raw)
The following patch-set fixes regressions caused by:
the commit "PCI: update bridge resources to get more big ranges when allocating space (again)"
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=da7822e5ad71ec9b745b412639f1e5e0ba795a20
patch 1/5: fix calculation of additional resource size for hotplug bridges
patch 2/5: ability to resize assigned pci-resource
patch 3/5: make SRIOV BARs resources optional
patch 4/5: make cardbus bridge resources optional
patch 5/5: code and terminology cleanup
The regression was caused on some platforms with limited i/o and memory
resources, the optional resources were allocated ahead of required resources,
thus starving the latter. The patchset ensures that all the required resources
are satisfied before any optional resources are satisfied.
Changelog: patch 2/5 is split into two patches. The changes corresponding to
resource.c is upstream; commit 23c570a67448e803408191f529ed9a83fd34a25a.
This patch has the remaining changes.
next reply other threads:[~2011-07-25 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 20:08 Ram Pai [this message]
2011-07-25 20:08 ` [PATCH 1/5 v3] PCI: honor child buses add_size in hot plug configuration Ram Pai
2011-08-01 18:52 ` Jesse Barnes
2011-07-25 20:08 ` [PATCH 2/5 v3] PCI : ability to relocate assigned pci-resources Ram Pai
2011-07-25 20:08 ` [PATCH 3/5 v3] PCI: make SRIOV resources optional Ram Pai
2011-07-25 20:08 ` [PATCH 4/5 v3] PCI: make cardbus-bridge " Ram Pai
2011-07-25 20:08 ` [PATCH 5/5 v3] PCI: code and comments cleanup Ram Pai
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=1311624522-30242-1-git-send-email-linuxram@us.ibm.com \
--to=linuxram@us.ibm.com \
--cc=bhelgaas@google.com \
--cc=bhutchings@solarflare.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=socketcan@hartkopp.net \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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