From: Yinghai Lu <yinghai@kernel.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ram Pai <linuxram@us.ibm.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH -v4 0/4] PCI : bridge resource reallocation patchset -- followup
Date: Thu, 23 Feb 2012 19:23:28 -0800 [thread overview]
Message-ID: <1330053812-10316-1-git-send-email-yinghai@kernel.org> (raw)
e084882: PCI: only enable pci realloc when SRIOV bar is not assigned
22f7543: PCI: print out suggestion about using pci=realloc
c81bbda: PCI: Make pci bridge reallocating enabled/disabled
b1b520d: PCI: Retry on type IORESOURCE_IO allocation.
are left over after Jesse pickup more of them.
it will try to auto detect if need to use pci=realloc, and print out suggestion.
could get from
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-next
-v3: Resend according to Jesse. Update ack and etc.
last one add CONFIG_PCI_REALLOC_ENABLE_DETECT according to Jesse.
-v4: left over that need refreshing against pci/linux-next...
resending accoring to Jesse.
Thanks
Yinghai
Documentation/kernel-parameters.txt | 9 +++-
drivers/pci/Kconfig | 10 +++++
drivers/pci/pci.c | 4 +-
drivers/pci/pci.h | 2 +-
drivers/pci/setup-bus.c | 75 +++++++++++++++++++++++++++--------
5 files changed, 79 insertions(+), 21 deletions(-)
next reply other threads:[~2012-02-24 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 3:23 Yinghai Lu [this message]
2012-02-24 3:23 ` [PATCH 1/4] PCI: Retry on type IORESOURCE_IO allocation Yinghai Lu
2012-02-24 3:23 ` [PATCH 2/4] PCI: Make pci bridge reallocating enabled/disabled Yinghai Lu
2012-02-24 3:23 ` [PATCH 3/4] PCI: print out suggestion about using pci=realloc Yinghai Lu
2012-02-24 3:23 ` [PATCH 4/4] PCI: only enable pci realloc when SRIOV bar is not assigned Yinghai Lu
2012-02-24 16:50 ` Jesse Barnes
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=1330053812-10316-1-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=linuxram@us.ibm.com \
--cc=torvalds@linux-foundation.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).