From: Bjorn Helgaas <bhelgaas@google.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-pci@vger.kernel.org, Myron Stowe <mstowe@redhat.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] pci, add FW_BUG warning to pci= kernel option
Date: Mon, 10 Nov 2014 20:59:02 -0700 [thread overview]
Message-ID: <20141111035902.GC28161@google.com> (raw)
In-Reply-To: <1414865479-25792-1-git-send-email-prarit@redhat.com>
[+cc lkml, linux-arch, Linus]
On Sat, Nov 01, 2014 at 02:11:19PM -0400, Prarit Bhargava wrote:
> The kernel should boot PCI without the use of kernel parameters. Display
> a FW_BUG warning when pci= is used.
>
> Cc: Myron Stowe <mstowe@redhat.com>
> Cc: linux-pci@vger.kernel.org
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> ---
> drivers/pci/pci.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 625a4ac..5172060b 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -4515,6 +4515,8 @@ static int __init pci_setup(char *str)
> }
> str = k;
> }
> + add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK);
> + pr_crit(FW_BUG "The PCI configuration has been overridden thorugh the use of pci=. Please report the issue you are attempting to resolve to your hardware vendor.\n");
My goal is to be able to boot without any "pci=" parameters, so from that
perspective, I like this.
When people have a problem booting Linux, they often try a variety of
things like "pci=assign-busses", "pci=nocrs", "pci=nomsi", "pci=nommconf",
"pci=noacpi", etc. If they find something that works, there's a tendency
to treat that as a "solution." I'd rather that they report it, so we can
try to fix the bug or add a quirk so the *next* person won't have to figure
out the right parameters to use.
My worry is that there are a few things where Linux isn't smart enough to
do the right thing automatically, and I don't think we'll have a good
solution in the near future. For example:
pci=norom
pci=pcie_bus_perf,pcie_bus_safe,etc.
pci=cbiosize=...
pci=cbmemsize=...
pci=resource_alignment=...
pci=hpiosize=...
pci=hpmemsize=...
pci=realloc
I don't like the fact that these options exist, but I suspect there are
users that do depend on them and might find this warning too aggressive.
So I'm interested in opinions on whether this is a good idea at all and
whether we should exclude some options from the warning/tainting.
Bjorn
> return 0;
> }
> early_param("pci", pci_setup);
> --
> 1.7.9.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-11 3:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 18:11 [PATCH] pci, add FW_BUG warning to pci= kernel option Prarit Bhargava
2014-11-11 3:59 ` Bjorn Helgaas [this message]
2014-11-17 23:42 ` Bjorn Helgaas
2014-11-18 12:42 ` Prarit Bhargava
2014-11-18 14:00 ` 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=20141111035902.GC28161@google.com \
--to=bhelgaas@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mstowe@redhat.com \
--cc=prarit@redhat.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).