From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linux-kernel@vger.kernel.org, Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: PCI: Correct the resource_alignment parameter example
Date: Thu, 6 Jun 2019 14:38:12 +1000 [thread overview]
Message-ID: <2994f354-29d4-b6cc-4ebd-d25fd0b2cad4@ozlabs.ru> (raw)
In-Reply-To: <20190606032557.107542-1-aik@ozlabs.ru>
Argh, it should have had "PATCH" in the subject, I broke my scripts so
they run git format-patch --subject-prefix="". Sorry. Repost?
On 06/06/2019 13:25, Alexey Kardashevskiy wrote:
> The option description requires an order and so does the option
> parsing code, however the example uses a size, fix this.
>
> Fixes: 8b078c603249 ("PCI: Update "pci=resource_alignment" documentation")
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 2b8ee90bb644..dcb53d64ad74 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -3340,27 +3340,28 @@
> resource_alignment=
> Format:
> [<order of align>@]<pci_dev>[; ...]
> Specifies alignment and device to reassign
> aligned memory resources. How to
> specify the device is described above.
> If <order of align> is not specified,
> PAGE_SIZE is used as alignment.
> PCI-PCI bridge can be specified, if resource
> windows need to be expanded.
> To specify the alignment for several
> instances of a device, the PCI vendor,
> device, subvendor, and subdevice may be
> - specified, e.g., 4096@pci:8086:9c22:103c:198f
> + specified, e.g., 12@pci:8086:9c22:103c:198f
> + for the 4096 alignment.
> ecrc= Enable/disable PCIe ECRC (transaction layer
> end-to-end CRC checking).
> bios: Use BIOS/firmware settings. This is the
> the default.
> off: Turn ECRC off
> on: Turn ECRC on.
> hpiosize=nn[KMG] The fixed amount of bus space which is
> reserved for hotplug bridge's IO window.
> Default size is 256 bytes.
> hpmemsize=nn[KMG] The fixed amount of bus space which is
> reserved for hotplug bridge's memory window.
> Default size is 2 megabytes.
> hpbussize=nn The minimum amount of additional bus numbers
>
--
Alexey
next prev parent reply other threads:[~2019-06-06 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 3:25 PCI: Correct the resource_alignment parameter example Alexey Kardashevskiy
2019-06-06 4:38 ` Alexey Kardashevskiy [this message]
2019-08-08 20:15 ` Bjorn Helgaas
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=2994f354-29d4-b6cc-4ebd-d25fd0b2cad4@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=helgaas@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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).