From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, <linuxppc-dev@ozlabs.org>
Subject: Re: [1/4] powerpc/pseries: Make PCI non-optional
Date: Thu, 15 Oct 2015 22:10:54 +1100 (AEDT) [thread overview]
Message-ID: <20151015111054.45C5D1402D6@ozlabs.org> (raw)
In-Reply-To: <1443681874-28145-1-git-send-email-mpe@ellerman.id.au>
On Thu, 2015-01-10 at 06:44:31 UTC, Michael Ellerman wrote:
> The pseries build with PCI=n looks to have been broken for at least 5
> years, and no one's noticed or cared.
>
> Following the obvious breakages backward, the first commit I can find
> that builds is the parent of 2eb4afb69ff3 ("powerpc/pci: Move pseries
> code into pseries platform specific area") from April 2009.
>
> A distro would never ship a PCI=n kernel, so it is only useful for folks
> building custom kernels. Also on KVM the virtio devices appear on PCI,
> so it would only be useful if you were building kernels specifically to
> run on PowerVM and with no PCI devices.
>
> The added code complexity, and testing load (which we've clearly not
> been doing), is not justified by the small reduction in kernel size for
> such a niche use case.
>
> So just make PCI non-optional on pseries.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Series applied to powerpc next.
https://git.kernel.org/powerpc/c/4c9cd468b348c9e47f9380a5
cheers
prev parent reply other threads:[~2015-10-15 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 6:44 [PATCH 1/4] powerpc/pseries: Make PCI non-optional Michael Ellerman
2015-10-01 6:44 ` [PATCH 2/4] powerpc/pseries: Remove use of CONFIG_PCI Michael Ellerman
2015-10-01 6:44 ` [PATCH 3/4] powerpc/pseries: Move PCI objects to obj-y Michael Ellerman
2015-10-01 6:44 ` [PATCH 4/4] powerpc/pseries: Drop always true CONFIG_PSERIES_MSI Michael Ellerman
2015-10-15 11:10 ` Michael Ellerman [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=20151015111054.45C5D1402D6@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.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).