From: okaya@codeaurora.org (okaya at codeaurora.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: Add pci=safemode option
Date: Sat, 02 Jun 2018 13:57:19 -0400 [thread overview]
Message-ID: <f3d6c44829910cb09c6f72dba1c41b39@codeaurora.org> (raw)
In-Reply-To: <20180602174307.GB14870@amd>
On 2018-06-02 13:43, Pavel Machek wrote:
> Hi!
>
>> > And you should explain what exactly in PCI is "optional". Who defines
>> > this and where is that list and what can go wrong if those options are
>> > not enabled?
>>
>> Bjorn and I discussed the need for such a "safe" mode feature when you
>> want to bring up PCI for a platform. You want to turn off everything
>> as
>> a starter and just stick to bare minimum.
>>
>> I can add a few words describing them. The goal of this option is to
>> keep
>> base PCI features with MSI only. Things like PME, AER, ASPM, Extended
>> Tags, LTR, Relaxed Ordering, SRIOV are all considered optional.
>> safemode
>> is certainly not intended for production environments.
>>
>> I can taint the kernel as a suggestion.
>
> I don't think tainting is required. even modern platforms should work
> in the safe mode.
Yeah, concern was getting used to the safe mode and never running the
full stack to fix the actual issues like getting away with crappy
hardware and firmware.
It becomes a support issue for the community.
> Pavel
prev parent reply other threads:[~2018-06-02 17:57 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
2018-06-02 17:43 ` Pavel Machek
2018-06-02 17:57 ` okaya at codeaurora.org [this message]
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=f3d6c44829910cb09c6f72dba1c41b39@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).