public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI / PCIe: Introduce command line option to disable ARI
Date: Wed, 29 Feb 2012 14:33:21 -0800	[thread overview]
Message-ID: <4F4EA7B1.9060607@xenotime.net> (raw)
In-Reply-To: <201202292309.42051.rjw@sisk.pl>

On 02/29/2012 02:09 PM, Rafael J. Wysocki wrote:

> From: Rafael J. Wysocki <rjw@sisk.pl>
> 
> There are PCIe devices on the market that report ARI support but
> then fail to initialize correctly when ARI is actually used.  This
> leads to situations in which kernels 2.6.34 and newer fail to handle
> systems where the previous kernels worked without any apparent
> problems.  Unfortunately, it is currently unknown how many such
> devices are there.
> 
> For this reason, introduce a new kernel command line option,
> pci=noari, allowing users to disable PCIe ARI altogether if they
> see problems with PCIe device initialization.
> 
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
>  drivers/pci/pci.c |    7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> Index: linux/drivers/pci/pci.c
> ===================================================================
> --- linux.orig/drivers/pci/pci.c
> +++ linux/drivers/pci/pci.c
> @@ -94,6 +94,9 @@ u8 pci_cache_line_size;
>   */
>  unsigned int pcibios_max_latency = 255;
>  
> +/* If set, the PCIe ARI capability will not be used. */
> +static bool pcie_ari_disabled;


Please update Documentation/kernel-parameters.txt .

-- 
~Randy

  reply	other threads:[~2012-02-29 22:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 22:09 [PATCH] PCI / PCIe: Introduce command line option to disable ARI Rafael J. Wysocki
2012-02-29 22:33 ` Randy Dunlap [this message]
2012-02-29 23:06   ` Rafael J. Wysocki

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=4F4EA7B1.9060607@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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