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  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, 21 Feb 2017 00:47:40 +0100
From:   "Rafael J. Wysocki" <>
To:     Viresh Kumar <>
Cc:     Linux PM <>,
        Srinivas Pandruvada <>,
        LKML <>,
        Jonathan Corbet <>,
        Linux Documentation <>
Subject: Re: [RFC][PATCH] cpufreq: User/admin documentation update and consolidation

On Monday, February 20, 2017 02:58:27 PM Rafael J. Wysocki wrote:
> On Monday, February 20, 2017 03:26:08 PM Viresh Kumar wrote:
> > On 18-02-17, 02:36, Rafael J. Wysocki wrote:
> > > +CPU Initialization
> > > +==================
> > > +
> > 
> > 
> > > +Next, the scaling driver's ``->init()`` callback is invoked with the policy
> > > +pointer of the new CPU passed to it as the argument.  If the policy object
> > > +pointed to by it is new
> > 
> > The callbacks don't need to do anything special for a new policy.
> > Infact, ->init() is only called for new policies or policies which
> > don't have any active CPUs as of now.
> Yes, it is called for new and inactive policies.
> For new policies it has to populate policy->cpus (because otherwise the core
> doesn't know what CPUs should be there), which quite arguably doesn't have
> to (or even doesn't need to) be done for inactive policies (because they already
> have policy->real_cpus and policy->related_cpus populated).
> I would even argue that ->init() should not update policy->cpus for inactive
> (but not new) policies.
> > > , that callback is expected to initialize the performance
> > > +scaling hardware interface for the given CPU (or, more precisely, for the set of
> > > +CPUs sharing the hardware interface it belongs to, represented by its policy
> > > +object) and to set parameters of the policy, like the minimum and maximum
> > > +frequencies supported by the hardware, the table of available frequencies (if
> > > +the set of supported P-states is not a continuous range), and the mask of CPUs
> > > +that belong to the same policy.
> > 
> > Maybe we should explicitly mention that both online and offline CPUs
> > should be set in the mask ?
> I can do that.
> But offline CPUs can only be set in that mask if the policy is actually new.

Well, drivers actually always set them, so let me put it differently.

It is not very useful to update a policy that previously was inactive from
->init(), because the related_cpus mask is only populated if the policy is new
and the symbolic links from CPU directories in sysfs to it are only created
once etc.

So it would be OK to skip updating the policy in ->init() in that case.


Powered by blists - more mailing lists