linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Gabriele Paoloni <gabriele.paoloni@huawei.com>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	linux-pci@vger.kernel.org, Keith Busch <keith.busch@intel.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Ingo Molnar <mingo@kernel.org>,
	Christoffer Dall <cdall@linaro.org>,
	Jonathan Corbet <corbet@lwn.net>,
	timur@codeaurora.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Dongdong Liu <liudongdong3@huawei.com>,
	David Rientjes <rientjes@google.com>,
	Thymo van Beers <thymovanbeers@gmail.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Frederick Lawler <fred@fredlawl.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	linux-arm-msm@vger.kernel.org,
	Frederic Weisbecker <frederic@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	Oza Pawandeep <poza@codeaurora.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [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.
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  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
2018-05-30  7:48         ` Greg Kroah-Hartman
2018-05-30  7:56           ` okaya
2018-05-30  8:22             ` okaya
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

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=bhelgaas@google.com \
    --cc=cdall@linaro.org \
    --cc=corbet@lwn.net \
    --cc=fred@fredlawl.com \
    --cc=frederic@kernel.org \
    --cc=gabriele.paoloni@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=helgaas@kernel.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=keith.busch@intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liudongdong3@huawei.com \
    --cc=marc.zyngier@arm.com \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=poza@codeaurora.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=thymovanbeers@gmail.com \
    --cc=timur@codeaurora.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).