Thursday, September 8, 2016

[fedora-arm] Re: Fedora 24 Mate Spin fails to start all cpus on Odroid-Xu4

Thanks Peter,

This will be very disappointing if we cannot enable all the cpus.

BTW, when you refer to upstream here, is it the Redhat team or the
Kernel team beyond?


On 09/08/2016 08:40 AM, Peter Robinson wrote:
> On Thu, Sep 8, 2016 at 1:19 PM, Stewart Samuels <> wrote:
>> Hi Peter,
>> I am not doing anything with the system other than booting up and logging
>> in. This is true for the Ubuntu build as well.
>> Where are these policies set and can you provide any me any direction for
>> documentation on them? seeming these are distro specific, I would expect
>> something relative to Fedora.
> Nope, they are upstream kernel (and possibly even upstream u-boot)
> specific. The only default we set in this regard that may, or may not,
> be Fedora specific is we use the On Demand governor as the default.
> This is architecture in dependent default across Fedora.
> I doubt the Ubuntu build ships an upstream mainline kernel but then I
> don't follow any of what they do so TBH not sure there, I also have no
> idea what they set their default policy to.
> So doing a quick google for "cpufreq" I get some of the following
> links that look remotely relevant, no idea how much they are, sorry.
>> On 09/08/2016 05:29 AM, Peter Robinson wrote:
>>> On Wed, Sep 7, 2016 at 8:44 PM, Stewart Samuels <>
>>> wrote:
>>>> Hi Peter,
>>>> Here is the result of lscpu.
>>>> ---------------------------------------------------------------------------------------
>>>> [root@myodroid ~]# lscpu
>>>> Architecture: armv7l
>>>> Byte Order: Little Endian
>>>> CPU(s): 8
>>>> On-line CPU(s) list: 0-4
>>>> Off-line CPU(s) list: 5-7
>>>> Thread(s) per core: 1
>>>> Core(s) per socket: 2
>>>> Socket(s): 2
>>>> Model name: ARMv7 Processor rev 3 (v7l)
>>>> CPU max MHz: 1300.0000
>>>> CPU min MHz: 200.0000
>>>> ----------------------------------------------------------------------------------------
>>>> Is there any way to enable these other cpus? My Ubuntu 16.04
>>>> installation
>>>> has them all enabled and the Ubuntu responsiveness is much quicker. I
>>>> suspect this has something to do with it.
>>> So it's shut them off, it's something with the way the big.LITTLE
>>> stuff works, so it's basically as expected. I believe it's handled as
>>> part of the cpufreq policies from user space but I've done little with
>>> the b.L stuff so I'm not sure. I'd try with the performance policy
>>> first.
>>> In terms of speed vs other distros, it would likely depend on a lot
>>> more than just the cores that are running but I have no idea what
>>> you're doing with it (remote server/desktop/what ever) so there's
>>> likely a lot that will come into play.
arm mailing list

No comments:

Post a Comment