Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a81b05f2 authored by Rick Yiu's avatar Rick Yiu Committed by DarkJoker360
Browse files

sched/fair: do not use boosted margin for prefer_high_cap case



For prefer_high_cap case, it will start from mid/max cpu already,
so there is no need to use boosted margin for task placement.

Bug: 160082718
Test: tasks scheduled as expected
Signed-off-by: default avatarRick Yiu <rickyiu@google.com>
Change-Id: I4df27b1e468484f5d9aedfa57ee444f397a8da81
parent 0d6e790c
Loading
Loading
Loading
Loading
+4 −2
Original line number Diff line number Diff line
@@ -7392,11 +7392,13 @@ static inline bool task_fits_capacity(struct task_struct *p,
	unsigned int margin;

	if (capacity_orig_of(task_cpu(p)) > capacity_orig_of(cpu))
		margin = schedtune_task_boost(p) > 0 ?
		margin = schedtune_task_boost(p) > 0 &&
			 !schedtune_prefer_high_cap(p) ?
			sched_capacity_margin_down_boosted[task_cpu(p)] :
			sched_capacity_margin_down[task_cpu(p)];
	else
		margin = schedtune_task_boost(p) > 0 ?
		margin = schedtune_task_boost(p) > 0 &&
			 !schedtune_prefer_high_cap(p) ?
			sched_capacity_margin_up_boosted[task_cpu(p)] :
			sched_capacity_margin_up[task_cpu(p)];