linux-kernel - Re: [PATCH V5 1/2] topology: Allow multiple entities to provide sched_freq

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Tue, 9 Mar 2021 09:46:43 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Will Deacon <will@...nel.org>
Cc:     Rafael Wysocki <rjw@...ysocki.net>,
        Catalin Marinas <catalin.marinas@....com>,
        Sudeep Holla <sudeep.holla@....com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>, linux-pm@...r.kernel.org,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Ionela Voinescu <ionela.voinescu@....com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V5 1/2] topology: Allow multiple entities to provide
 sched_freq_tick() callback

On 08-03-21, 14:52, Will Deacon wrote:
> On Mon, Mar 01, 2021 at 12:21:17PM +0530, Viresh Kumar wrote:
> > +EXPORT_SYMBOL_GPL(topology_set_scale_freq_source);
> 
> I don't get why you need to export this in this patch. The arm64 topology
> code is never built as a module.
> 
> > +EXPORT_SYMBOL_GPL(topology_clear_scale_freq_source);
> 
> Same here.
> 
> > +EXPORT_SYMBOL_GPL(freq_scale);
> 
> And here.

After this patch, any part of the kernel can use these
helpers/variables to run their own implementation of tick-freq-scale
and so this patch looked to be the right place for that to me.

And the second patch in the series updates the CPPC cpufreq driver
(tristate) to use these exported symbols, so we have the first user
who needs the exported symbols as well.

> This one probably wants a less generic name as well if it's going
> to be exported.

x86 names it arch_freq_scale, perhaps we should stick to that instead.

-- 
viresh