linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Marc Dietrich <marvin24@gmx.de>
Cc: linuxppc-dev@lists.ozlabs.org, Geoff Levand <geoff@infradead.org>
Subject: Re: Time to remove platforms/cell?
Date: Thu, 17 Sep 2015 19:45:38 +1000	[thread overview]
Message-ID: <1442483138.26748.4.camel@ellerman.id.au> (raw)
In-Reply-To: <2023345.Irprl084gX@fb07-iapwap2>

On Thu, 2015-09-17 at 10:43 +0200, Marc Dietrich wrote:
> Am Donnerstag, 17. September 2015, 15:28:47 schrieb Michael Ellerman:
> > Discuss ...
> 
> as long as Geoff still maintains the ps3 port - why?

Because even if Geoff maintains the ps3 port, there's still a non-zero cost to
us for carrying the Cell code.

To be clear there's more to Cell than just ps3. The platforms/cell code is
mainly about supporting the IBM Cell Blades, as well as spufs, which is also
used on ps3.

See for example commit 74b5037baa20 ("powerpc/mm: Fix pte_pagesize_index()
crash on 4K w/64K hash"):

  https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=74b5037baa2011a2799e2c43adde7d171b072f9e

Which is a fix for crashes we were seeing on non-cell machines, caused by some
obscure code that was added for Cell. It took several of us a few days to track
that one down.

But the main motivation would just be to drop code that no one's using. From
December 2013 until April 2015 the Cell machines (not ps3) were broken in
mainline and no one noticed. I now have automated boot tests to prevent that
happening again, but it makes me think no one is using those machines much
anymore.


You also raise a good point, which is that ps3 is a separate platform, so we
could actually keep that but get rid of platforms/cell. If we did that we'd
need to move spufs out of platforms/cell though.

Looking at the code size:

	platforms/ps3	 	 6 KSLOC
	platforms/cell		11 KSLOC
	platforms/cell/spufs	 7 KSLOC
	other cell code		 2 KSLOC

So dropping platforms/cell but not ps3 would save us ~6 KSLOC.


Having said all that, this email was mainly a fishing expedition to see if
anyone still cares about Cell support at all. It sounds like you at least are
running mainline kernels on PS3?

cheers

  parent reply	other threads:[~2015-09-17  9:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  5:28 Time to remove platforms/cell? Michael Ellerman
2015-09-17  8:43 ` Marc Dietrich
2015-09-17  9:31   ` Arnd Bergmann
2015-09-17 10:05     ` Michael Ellerman
2015-09-17 11:01       ` Arnd Bergmann
2015-09-17 17:50       ` Geoff Levand
2015-09-17  9:45   ` Michael Ellerman [this message]
2015-09-17 10:28     ` Marc Dietrich
2015-09-17 11:15       ` Arnd Bergmann
2015-09-21  9:42         ` Michael Ellerman
2015-09-21  9:44       ` Michael Ellerman
2015-10-04 19:27       ` Geoff Levand
2015-10-05 10:27         ` Marc Dietrich
2015-10-07 17:20           ` Geoff Levand
2015-10-08 18:10             ` Geoff Levand
2015-10-09 17:45               ` Geoff Levand
2015-10-09 21:13                 ` Marc Dietrich
2015-10-22 19:15                   ` Geoff Levand
2015-10-23  1:54                     ` Michael Ellerman
2015-10-23  8:00                       ` Marc Dietrich

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=1442483138.26748.4.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=geoff@infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=marvin24@gmx.de \
    /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).