From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: Add pci=safemode option
Date: Sat, 2 Jun 2018 19:43:07 +0200 [thread overview]
Message-ID: <20180602174307.GB14870@amd> (raw)
In-Reply-To: <6c317ed8-cca3-8862-5f3b-12cf14e4d53b@codeaurora.org>
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.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180602/317d320c/attachment.sig>
next prev parent reply other threads:[~2018-06-02 17:43 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 [this message]
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=20180602174307.GB14870@amd \
--to=pavel@ucw.cz \
--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).