From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: Add pci=safemode option
Date: Wed, 30 May 2018 11:28:42 -0400 [thread overview]
Message-ID: <2a5281cd-a0c7-1449-5b72-133660667fa6@codeaurora.org> (raw)
In-Reply-To: <20180530145650.GA39853@bhelgaas-glaptop.roam.corp.google.com>
On 5/30/2018 10:56 AM, Bjorn Helgaas wrote:
> This *was* my idea, but I'm starting to think it was a bad idea.
>
> I don't want people to use pci= parameters as the normal way to get a
> system to boot. That would be a huge support hassle (putting things
> in release notes, diagnosing problems when people forget it, etc).
>
> But the parameters *are* useful for debugging. If we had a
> "pci=safemode" and it avoided some problem, the next step would be to
> narrow it down by using the more specific flags (pci=nomsi, pci=noari,
> pci=no_ext_tags, etc). So I think 95% of the value is in the specific
> flags, and a "pci=safemode" might add a little bit of value but at the
> cost of a small but nagging maintenance concern and code clutter.
OK. Let's try noXYZ feature. Can you enumerate the XYZ features that you
want to see?
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-05-30 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 3:19 [PATCH] PCI: Add pci=safemode option Sinan Kaya
2018-05-30 4:31 ` Greg Kroah-Hartman
2018-05-30 4:41 ` Sinan Kaya
2018-05-30 4:55 ` Greg Kroah-Hartman
2018-05-30 7:37 ` Christoph Hellwig
2018-05-30 7:44 ` okaya at codeaurora.org
2018-05-30 7:48 ` Greg Kroah-Hartman
2018-05-30 7:56 ` okaya at codeaurora.org
2018-05-30 8:22 ` okaya at codeaurora.org
2018-05-30 14:56 ` Bjorn Helgaas
2018-05-30 15:28 ` Sinan Kaya [this message]
2018-06-02 17:43 ` Pavel Machek
2018-06-02 17:57 ` okaya at codeaurora.org
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=2a5281cd-a0c7-1449-5b72-133660667fa6@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).