Lines Matching refs:UCLAMP_MAX

29         * UCLAMP_MAX, which sets the upper bound.
32 of the system. UCLAMP_MIN implies boosting a task, while UCLAMP_MAX implies
215 The rq has a bucket for each uclamp_id tunables: [UCLAMP_MIN, UCLAMP_MAX].
235         p->uclamp[UCLAMP_MAX] = 1024
238 4 will be incremented for UCLAMP_MAX to reflect the fact the rq has a task in
250         // repeat for UCLAMP_MAX
258         // repeat for UCLAMP_MAX
280         p0->uclamp[UCLAMP_MAX] = 900
283         p1->uclamp[UCLAMP_MAX] = 500
286 and UCLAMP_MAX become:
291         rq->uclamp[UCLAMP_MAX] = max(900, 500) = 900
295 particular for UCLAMP_MAX hint when user space would like to save power.
405         p0->uclamp[UCLAMP_MAX] = // system default;
408         p1->uclamp[UCLAMP_MAX] = 50% * 1024;
421         p0->uclamp[UCLAMP_MAX] = cgroup0->cpu.uclamp.max = 60% * 1024;
424         p1->uclamp[UCLAMP_MAX] = 50% * 1024; // intact
431         p0->uclamp[UCLAMP_MAX] = cgroup1->cpu.uclamp.max = 100% * 1024;
434         p1->uclamp[UCLAMP_MAX] = 50% * 1024; // intact
458 System wide limit of allowed UCLAMP_MAX range. By default it is set to 1024,
459 which means that permitted effective UCLAMP_MAX range for tasks is [0:1024].
472 won't be satisfied until it is more than p->uclamp[UCLAMP_MAX].
486         p_fair->uclamp[UCLAMP_MAX] = 1024
497         p_rt->uclamp[UCLAMP_MAX] = 1024
567 UCLAMP_MAX for some background tasks that don't care about performance but
606         p0->uclamp[UCLAMP_MAX] = 512
612         p1->uclamp[UCLAMP_MAX] = 1024
619         rq->uclamp[UCLAMP_MAX] = max(512, 1024) = 1024
629 5.2. UCLAMP_MAX can break PELT (util_avg) signal
633 there's always some idle time on the CPU. But with UCLAMP_MAX, this frequency
646         p0->uclamp[UCLAMP_MAX] = 0
655         rq->uclamp[UCLAMP_MAX] = 0
690         p1->uclamp[UCLAMP_MAX] = 1024
692 then the effective UCLAMP_MAX for the CPU will be 1024 according to max
702         rq->uclamp[UCLAMP_MAX] = 1024