8 core update for exynos? !

Search This thread

Andmoreagain

Senior Member
Dec 19, 2013
101
191
Noticed this while looking at the latest patches from the Linaro guys... big.LITTLE MP seems to have been acheived and confirmed working on the exynos5420-powered peach-pit board (Samsung Chromebook). Patches/discussion:

Problems booting exynos5420 with >1 CPU
(1/3) ARM: MCPM: provide infrastructure to allow for MCPM loopback
(2/3) ARM: TC2: test the MCPM loopback during boot
(3/3) ARM: exynos: activate the CCI on boot CPU/cluster with the MCPM loopback

Thank you very much for posting! With your series I'm able to boot
all 8 cores on exynos5420-peach-pit and exynos5800-peach-pi sitting on
my desk.

Tested-by: Doug Anderson <dianders@chromium.org>
 
  • Like
Reactions: Freakstyler

mohamadreza33

Senior Member
Jul 9, 2014
134
74
Tehran
Its dangerous...

So...., are we getting this 8 core update or what?

i read in some other community... they activated the 8 cores in the same time.. and after 1 hour their device had been damaged hardly and burned.. i suggest you do not activate the 8 cores in the same time.. because the voltage of both CPU are not same... and its very dangerous :rolleyes::eek:
 
  • Like
Reactions: Ahmedmoataz

Andmoreagain

Senior Member
Dec 19, 2013
101
191
i read in some other community... they activated the 8 cores in the same time.. and after 1 hour their device had been damaged hardly and burned.. i suggest you do not activate the 8 cores in the same time.. because the voltage of both CPU are not same... and its very dangerous :rolleyes::eek:

Sources? For some reason I highly doubt this is true for the Exynos 5420 because (as far as I know) community devs have not been able to activate Global Task Scheduling/big.LITTLE-MP on our SoC prior to the patchset I linked to in my previous post. Another thing to note is that the Linaro big.LITTLE-MP patchset is not applicable to the current stock kernel for our device. The official SM-P600 kernel is at version 3.4.39 while the Linaro Stable Kernel is at version 3.10.x.

Either way, as far as my understanding of the big.LITTLE technology goes, the GTS (formerly known as HMP) solution shouldn't cause our device to heat up more than the current IKS solution if correctly implemented.

See:

Heterogenous Multi-Processing Solution of Exynos 5 Octa with ARM® big.LITTLE™ Technology
Benefits of the big.LITTLE Architecture
Software Techniques for ARM big.LITTLE Systems

tl;dr: The patchset is already here (thanks to the devs @ Linaro) and can be implemented on development boards running on big.LITTLE architecture. Implementing it properly in our device's kernel is a different story...
 
Last edited:

technobuddha

Member
Feb 8, 2014
22
2
Another thing to note is that the Linaro big.LITTLE-MP patchset is not applicable to the current stock kernel for our device. The official SM-P600 kernel is at version 3.4.39 while the Linaro Stable Kernel is at version 3.10.x.

tl;dr: The patchset is already here (thanks to the devs @ Linaro) and can be implemented on development boards running on big.LITTLE architecture. Implementing it properly in our device's kernel is a different story...

Hi all,
I've been researching this, as I plan on building a ROM for the samsung galaxy tab pro 12.2
I want to have both android and linux (xwindows) running side by side.
So I want to make sure that this big-LITTLE-MP patch works.

I'm trying to find out if samsung has applied the patch or already has the capibility to run all 8.. well with the 'scheduler" anyways in their original ROM. I want to port it, and add a chroot linux to it, with set of libraries that will have xwindows.

I'm learning how to busybox/chroot a linux inside android, but ultimately i want the chroot linux to be able to use the big-LITTLE-MP scheduler capibilities alongside android.

I'm a big confused as to how to accomplish this. when you chroot into a jailed linux, you don't need a kernel. so is the existing kernel used?
I believe so, and if that is true, then to have the xwindows, I have to make sure i have the proper mali hardware blobs for xwindows. correct?

and one of the biggest challanges is to let xwindows use the touchscreen.

am I asking for too much? is this even possible? and if so, where should I start looking for info for this project?

thanks!
 
  • Like
Reactions: Alexsandra

kcrudup

Senior Member
Mar 27, 2007
1,517
749
San Francisco Bay Area
Another thing to note is that the Linaro big.LITTLE-MP patchset is not applicable to the current stock kernel for our device. The official SM-P600 kernel is at version 3.4.39 while the Linaro Stable Kernel is at version 3.10.x. ... Implementing it properly in our device's kernel is a different story
I looked at the patches- it could be done by any competent kernel dev soon enough.
 

3c

Senior Member
Jul 19, 2005
2,937
2,062
www.3c71.com
No HMP in Galaxy Tab S Exynos 5420

Just to confirm some of the posts, HMP is not enabled in Tab S (10.5) and only 4 cores can be seen at any time. Big(no little) deception as this tab was supposed to replace a fully HMP enabled S5.

This could possibly confirm E5420+HMP = E5422 or simply that kernel is not HMP-enabled.
 

3c

Senior Member
Jul 19, 2005
2,937
2,062
www.3c71.com
HMP in Note 3 Neo with 4+2

I tested using 3C Toolbox, which shows all 8 (or 6) cores running if available. The same discovery method worked on both the S5 (SM-G900H) and the Note 3 Neo (SM-N7505).

See 3C Toolbox's CPU Manager screenshots taken on both S5 and Neo.
 

Attachments

  • Screenshot_2014-09-16-10-45-04.png
    Screenshot_2014-09-16-10-45-04.png
    126.2 KB · Views: 638
  • Screenshot_2014-08-05-12-17-20.png
    Screenshot_2014-08-05-12-17-20.png
    248.4 KB · Views: 607
  • Screenshot_2014-08-05-12-17-51.png
    Screenshot_2014-08-05-12-17-51.png
    247.9 KB · Views: 629
  • Screenshot_2014-08-25-11-34-39.png
    Screenshot_2014-08-25-11-34-39.png
    142.8 KB · Views: 584
Last edited:

mentaluproar

Member
Sep 22, 2014
12
0
So we really can expect HMP on this tablet? Excellent! I wonder how apps like BOINC would fare with the extra power. Could the tablet handle it?
 
Last edited:

Andmoreagain

Senior Member
Dec 19, 2013
101
191
So we really can expect HMP on this tablet? Excellent! I wonder how apps like BOINC would fare with the power. Could the tablet handle it?

Of course it can handle it. The rest is really just up to samsung whether they decide to roll out Linux 3.10+ for our device. Alternatively someone could simply backport the patchset from Linaro to Linux 3.4 or compile an actual 3.10+ kernel that boots on the SM-P600.

On a similar note, I recently tested Linux 3.14 with the normal IKS configuration (based on Samsung's defconfig for the SM-P600 with some updated values from the config for the Arndale Octa - an Exynos5420 dev board) but while it compiles just fine it doesn't get past the stock Samsung bootloader, and I'm sure there are some drivers missing as well. The only stuff I have currently merged in are the proprietary ARM Mali gpu drivers.

If I remember correctly dorimanx managed to get the 3.14 kernel to work with AOSP on the SGS2 but I'm not quite sure how he went about it and I'm too much of a kernel newbie to figure it out myself. If anyone here has any suggestions it would be deeply appreciated. Source: http://github.com/sigma-1/linux-linaro-3.14
 
  • Like
Reactions: DeBoX and 3c

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    I have had my Note 2014 (32GB) for two days and would not want to have both core sets running at the same time. The device can already get very warm in the SOC area and the battery drains just like my iPad 4 when playing 3D games- faster than I want it to. Games are smooth and ditto for apps, so not seeing an advantage of all eight, but see the two key disadvantages. Not running into any core hand-off issues some are reporting that can cause lag. Not yet anyway.


    Added:

    I use Nova for my launcher, since IMO much better than Samsung's. Based on performance, I see no reason for me to root the 2014. Very happy already, so see no need to rock the boat.

    It is completely false to say that HMP would impact battery, if anything the opposite is true. There are very few applications which could even in principle use all 8 cores. Instead most of the times 3 is where apps max out, which would make little sense to enable HMP for performance reasons. But it makes all the sense in the world to enable it for battery reasons.

    Samsung released a video a couple of months ago showing just that. Having all 8 cores enabled at the same time means that you have the 4 little one take most of the workload and the 4 big ones only be enabled as needed. This would result in unbelievable battery savings. Imagine an occasion where 4 little cores are not enough, what does the current implementation of big.little does? Oh but enable the 4 big cores disabling the little ones, so it ends up at times to light all 4 big cores when 4 little ones + 1 big one would be enough, this results in far lower battery.

    HMP is a great idea both in paper and in practice, see the new Note Neo, it's using HMP to perfection and manages with "lower" hardware to perform as well as it's elder brother as well as be more energy efficient. *This* should be our example. Exynos 5420 is HMP compatible and it would only take a dev to enable it. I don't think that it will happen, but *if* it will it would instantly lead to far better devices...

    Note 2014 has rather mediocre battery, my gf's ipad mini with almost half the MAHs has more juice. That's partly because the exynos chip is not very energy efficient. Enable all 8 cores and it will become that...

    BTW the Note Neo sources (with HMP enabled) were just released. If we had a more active community I would expect an HMP patch coming from the community soon. Sadly seeing how badly misinformed most people are about HMP I don't think anyone would put the effort required and we'd stay with gimped devices ... oh well.
    2
    So we really can expect HMP on this tablet? Excellent! I wonder how apps like BOINC would fare with the power. Could the tablet handle it?

    Of course it can handle it. The rest is really just up to samsung whether they decide to roll out Linux 3.10+ for our device. Alternatively someone could simply backport the patchset from Linaro to Linux 3.4 or compile an actual 3.10+ kernel that boots on the SM-P600.

    On a similar note, I recently tested Linux 3.14 with the normal IKS configuration (based on Samsung's defconfig for the SM-P600 with some updated values from the config for the Arndale Octa - an Exynos5420 dev board) but while it compiles just fine it doesn't get past the stock Samsung bootloader, and I'm sure there are some drivers missing as well. The only stuff I have currently merged in are the proprietary ARM Mali gpu drivers.

    If I remember correctly dorimanx managed to get the 3.14 kernel to work with AOSP on the SGS2 but I'm not quite sure how he went about it and I'm too much of a kernel newbie to figure it out myself. If anyone here has any suggestions it would be deeply appreciated. Source: http://github.com/sigma-1/linux-linaro-3.14
    2
    Here's your HMP. You just need to buy a device with Exynos 5422 (we have 5420) to get it. ;)
    Samsung announced two new mobile SoCs at MWC today. The first is an update to the Exynos 5 Octa with the new Exynos 5422. The 5422 is a mild update to the 5420, which was found in some international variants of the Galaxy Note 3. The new SoC is still built on a 28nm process at Samsung, but enjoys much higher frequencies on both the Cortex A7 and A15 clusters. The two clusters can run their cores at up to 1.5GHz and 2.1GHz, respectively.

    The 5422 supports HMP (Heterogeneous Multi-Processing), and Samsung LSI tells us that unlike the 5420 we may actually see this one used with HMP enabled. HMP refers to the ability for the OS to use and schedule threads on all 8 cores at the same time, putting those threads with low performance requirements on the little cores and high performance threads on the big cores.

    http://www.anandtech.com/show/7811/samsungs-exynos-5422-the-ideal-biglittle-exynos-5-hexa-5260
    1
    aac and ac3 seem to cause the most problems SD and HD. I generally keep the nitrate around 2.5 Mb/s just for portability sake. container doesn't matter as avi, mkv, and mp4 all have the drops. I've used mx, BS, Archos, xbmc, and a few others and installed custom codecs if needed. heck even Netflix has a few frame drops. maybe I'm just too sensitive to it, but my s4, gn2, and gn8 have no problems. my old gn10.1 had no problems either. this 10.1 2014 is also the first Samsung device I've had that doesn't natively support ac3. hardware playback with alternative players do play the ac3 audio, but with dropped frames.
    1
    My undergrad is computer electronics (though over ten years ago). Tech has changed a lot, but laws of electrical physics have stayed constant. Saying it is completely false seems as scientifically dubious as saying it is completely true. Samsung was concerned about thermals with the current devices. Seems that ties with likely more sustained peak watt consumption, so warmer running and more potential for battery consumption.

    With the current SOC being a 28 nM build, how does higher performance not equal more heat and less battery? Respectfully does not add up. Added: Unless the nM goes down in correlation to increased speed which can not be the case. That is unless the core mix results in an exponential speed curve, which would also be very unlikely.

    Again, the premise of point here is in regard to faster performance and not power efficency.

    Added 2 : BarryH does a fine job of articulating. The benefit would be efficiency and not a speed boost that would not come with a thermal and battery life cost, since the fixed constant is the 28nM.