Hi Rafael, On Tuesday 13 Oct 2020 at 13:53:37 (+0200), Rafael J. Wysocki wrote: > On Tue, Oct 13, 2020 at 12:01 AM Ionela Voinescu > <ionela.voinescu@xxxxxxx> wrote: > > > > Hey Lukasz, > > > > I think after all this discussion (in our own way of describing things) > > we agree on how the current cpufreq based FIE implementation is affected > > in systems that use hardware coordination. > > > > What we don't agree on is the location where that implementation (that > > uses the new mask and aggregation) should be. > > > > On Monday 12 Oct 2020 at 19:19:29 (+0100), Lukasz Luba wrote: > > [..] > > > The previous FIE implementation where arch_set_freq_scale() > > > was called from the drivers, was better suited for this issue. > > > Driver could just use internal dependency cpumask or even > > > do the aggregation to figure out the max freq for cluster > > > if there is a need, before calling arch_set_freq_scale(). > > > > > > It is not perfect solution for software FIE, but one of possible > > > when there is no hw counters. > > > > > [..] > > > > > Difference between new FIE and old FIE (from v5.8) is that the new one > > > purely relies on schedutil max freq value (which will now be missing), > > > while the old FIE was called by the driver and thus it was an option to > > > fix only the affected cpufreq driver [1][2]. > > > > > > > My final argument is that now you have 2 drivers that would need this > > support, next you'll have 3 (the new mediatek driver), and in the future > > there will be more. So why limit and duplicate this functionality in the > > drivers? Why not make it generic for all drivers to use if the system > > is using hardware coordination? > > > > Additionally, I don't think drivers should not even need to know about > > these dependency/clock domains. They should act at the level of the > > policy, which in this case will be at the level of each CPU. > > The policies come from the driver, though. > > The driver decides how many CPUs will be there in a policy and how to > handle them at the initialization time. Yes, policies are built based on information populated from the drivers at .init(): what CPUs will belong to a policy, what methods to use for setting and getting frequency, etc. So they do pass this information to the cpufreq core to be stored at the level of the policy, but later drivers (in the majority of cases) will not need to store on their own information on what CPUs belong to a frequency domain, they rely on having passed that information to the core, and the core mechanisms hold this information on the clock domains (currently through policy->cpus and policy->related_cpus). > > The core has no idea whether or not there is HW coordination in the > system, the driver is expected to know that and take that into > account. > Given that multiple drivers could use hardware coordination, and drivers already have a way to pass information about the type of coordination to the core through policy->shared_type, could there be a case for supporting this in the core, rather than the drivers? In my head I'm finding this option better compared to having a select set of drivers that would instruct the core to build the policies per-cpu, while holding in the driver information about what CPUs actually belong to clock domains. Additionally, the cpufreq core will have to be able to present to other frameworks (scheduler, thermal) this mask when requested, through a cpufreq interface function. So in the end we'll still potentially end up passing on this information from the driver to the core and then to the user. > Accordingly, it looks like there should be an option for drivers to > arrange things in the most convenient way (from their perspective) and > that option has gone away now. IMO, even if this hardware coordination support is entirely managed by the driver, one requirement is that other subsystems would be able to acquire information about dependent cpus. The scheduler FIE should just be another one of those users, with the decision on how that information is handled residing in architecture code (arch_set_freq_scale()). Architecture code might decide to have a default way of handling these cases or not to support them at all. Thank you, Ionela.
