From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Yinghai Lu <yinghai@kernel.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
Subject: Re: [PATCH 4/4] PCI: only enable pci realloc when SRIOV bar is not assigned
Date: Fri, 24 Feb 2012 08:50:05 -0800 [thread overview]
Message-ID: <20120224085005.59f55ff5@jbarnes-desktop> (raw)
In-Reply-To: <1330053812-10316-5-git-send-email-yinghai@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
On Thu, 23 Feb 2012 19:23:32 -0800
Yinghai Lu <yinghai@kernel.org> wrote:
> If bios does not assign those BAR or wrong address, then kernel will
> try to do pci realloc.
>
> in that case, user still can use pci=realloc=off to override it.
>
> -v2: According to Jesse, adding one CONFIG option for distribution to
> disable it or enable it.
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> ---
Ok applied these, thanks for the cleanups Yinghai.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-24 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 3:23 [PATCH -v4 0/4] PCI : bridge resource reallocation patchset -- followup Yinghai Lu
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 [this message]
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=20120224085005.59f55ff5@jbarnes-desktop \
--to=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 \
--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;
as well as URLs for NNTP newsgroup(s).