On Tue, Jan 22, 2019 at 12:02 PM Patrick Bellasi <patrick.bellasi@xxxxxxx> wrote: > > On 22-Jan 11:37, Rafael J. Wysocki wrote: > > On Tuesday, January 15, 2019 11:15:05 AM CET Patrick Bellasi wrote: [cut] > > > > IMO it would be better to combine this patch with the next one. > > Main reason was to better document in the changelog what we do for the > two different classes... > > > At least some things in it I was about to ask about would go away > > then. :-) > > ... but if it creates confusion I can certainly merge them. > > Or maybe clarify better in this patch what's not clear: may I ask what > were your questions ? > > > Besides, I don't really see a reason for the split here. > > Was mainly to make the changes required for RT more self-contained. > > For that class only, not for FAIR, we have additional code in the > following patch which add uclamp_default_perf which are system > defaults used to track/account tasks requesting the maximum frequency. > > Again, I can either better clarify the above patch or just merge the > two together: what do you prefer ? Merge the two together, please.
