From: Andrew Murray <andrew.murray@arm.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: Rob Landley <rob@landley.net>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jon Mason <jdmason@kudzu.us>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
"jiang.liu@huawei.com" <jiang.liu@huawei.com>
Subject: Re: [PATCH] PCI: Document PCIE BUS MPS parameters
Date: Wed, 23 Jan 2013 09:21:50 +0000 [thread overview]
Message-ID: <20130123092150.GA25603@arm.com> (raw)
In-Reply-To: <1358928096-29008-1-git-send-email-wangyijing@huawei.com>
On Wed, Jan 23, 2013 at 08:01:36AM +0000, Yijing Wang wrote:
> Document PCIE BUS MPS parameters pcie_bus_tune_off, pcie_bus_safe,
> pcie_bus_peer2peer, pcie_bus_perf into Documentation/kernel-parameters.txt.
> These parameters were introduced by Jon Mason <mason@myri.com> at
> commit 5f39e6705 and commit b03e7495a8. Document these into
> kernel-parameters.txt help users to understand and use the parameters.
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> ---
> Documentation/kernel-parameters.txt | 13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 363e348..4dfa8d2 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -2227,6 +2227,19 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> This sorting is done to get a device
> order compatible with older (<= 2.4) kernels.
> nobfsort Don't sort PCI devices into breadth-first order.
> + pcie_bus_tune_off [X86] Disable PCI-E MPS turning and using
> + the BIOS configured MPS defaults.
> + pcie_bus_safe [X86] Use the smallest common denominator MPS
> + of the entire tree below a root complex for every device
> + on that fabric. Can avoid inconsistent mps problem caused
> + by hotplug.
> + pcie_bus_perf [X86] Configure pcie device MPS to the largest
> + allowable MPS based on its parent bus.Improve performance
> + as much as possible.
> + pcie_bus_peer2peer [X86] Make the system wide MPS the smallest
> + possible value (128B).This configuration could prevent it
> + from working by having the MPS on one root port different
> + than the MPS on another.
> cbiosize=nn[KMG] The fixed amount of bus space which is
> reserved for the CardBus bridge's IO window.
> The default value is 256 bytes.
>
I was searching for documentation on this the other day.
It's not just X86 that use these options, PowerPC and Tile also use them (grep
for users of pcie_bus_configure_settings). I've also noticed a call to it from
hotplug as well...
In addition these options also have an effect on MRRS - I've not figured out
what effect they have, but you can look in drivers/pci/probe.c at the
pcie_write_mrrs function.
Andrew Murray
next prev parent reply other threads:[~2013-01-23 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 8:01 [PATCH] PCI: Document PCIE BUS MPS parameters Yijing Wang
2013-01-23 9:21 ` Andrew Murray [this message]
2013-01-23 10:13 ` Yijing Wang
2013-01-23 10:30 ` Andrew Murray
2013-01-23 11:44 ` Yijing Wang
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=20130123092150.GA25603@arm.com \
--to=andrew.murray@arm.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=jdmason@kudzu.us \
--cc=jiang.liu@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rob@landley.net \
--cc=wangyijing@huawei.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