linux-kernel - Re: [PATCH v5 02/17] ARM: Revert back to default scheduler topology.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200813191614.GB2337490@gmail.com>
Date:   Thu, 13 Aug 2020 21:16:14 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Valentin Schneider <valentin.schneider@....com>
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Russell King <linux@...linux.org.uk>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        peterz@...radead.org, vincent.guittot@...aro.org,
        morten.rasmussen@....com, Quentin Perret <qperret@...gle.com>
Subject: Re: [PATCH v5 02/17] ARM: Revert back to default scheduler topology.


* Valentin Schneider <valentin.schneider@....com> wrote:

> The ARM-specific GMC level is meant to be built using the thread sibling
> mask, but no devicetree in arch/arm/boot/dts uses the 'thread' cpu-map
> binding. With SD_SHARE_POWERDOMAIN gone, this topology level can be
> removed, at which point ARM no longer benefits from having a custom defined
> topology table.
> 
> Delete the GMC topology level by making ARM use the default scheduler
> topology table. This essentially reverts commit
> 
>   fb2aa85564f4 ("sched, ARM: Create a dedicated scheduler topology table")
> 
> Cc: Russell King <linux@...linux.org.uk>
> Suggested-by: Dietmar Eggemann <dietmar.eggemann@....com>
> Reviewed-by: Dietmar Eggemann <dietmar.eggemann@....com>
> Signed-off-by: Valentin Schneider <valentin.schneider@....com>

Minor changelog nit, it's helpful to add this final sentence:

    No change in functionality is expected.

( If indeed no change in functionality is expected. ;-)

Thanks,

	Ingo