sched/core: Fix typos in comments

 *

 * Normal scheduling state is serialized by rq->lock. __schedule() takes the

 * local CPU's rq->lock, it optionally removes the task from the runqueue and

 * always looks at the local rq data structures to find the most elegible task

 * always looks at the local rq data structures to find the most eligible task

 * to run next.

 *

 * Task enqueue is also under rq->lock, possibly taken from another CPU.

	/*

	 * Atomically grab the task, if ->wake_q is !nil already it means

	 * its already queued (either by us or someone else) and will get the

	 * it's already queued (either by us or someone else) and will get the

	 * wakeup due to that.

	 *

	 * In order to ensure that a pending wakeup will observe our pending

		return false;

	/*

	 * If there are more than one RR tasks, we need the tick to effect the

	 * If there are more than one RR tasks, we need the tick to affect the

	 * actual RR behaviour.

	 */

	if (rq->rt.rr_nr_running) {

	 * accounting was performed at enqueue time and we can just return

	 * here.

	 *

	 * Need to be careful of the following enqeueue/dequeue ordering

	 * Need to be careful of the following enqueue/dequeue ordering

	 * problem too

	 *

	 *	enqueue(taskA)

	 *	// sched_uclamp_used gets enabled

	 *	enqueue(taskB)

	 *	dequeue(taskA)

	 *	// Must not decrement bukcet->tasks here

	 *	// Must not decrement bucket->tasks here

	 *	dequeue(taskB)

	 *

	 * where we could end up with stale data in uc_se and

#ifdef CONFIG_SMP

	if (p->sched_class->task_woken) {

		/*

		 * Our task @p is fully woken up and running; so its safe to

		 * Our task @p is fully woken up and running; so it's safe to

		 * drop the rq->lock, hereafter rq is only used for statistics.

		 */

		rq_unpin_lock(rq, rf);

	/*

	 * If the owning (remote) CPU is still in the middle of schedule() with

	 * this task as prev, wait until its done referencing the task.

	 * this task as prev, wait until it's done referencing the task.

	 *

	 * Pairs with the smp_store_release() in finish_task().

	 *

#ifdef CONFIG_SMP

	if (p->sched_class->task_woken) {

		/*

		 * Nothing relies on rq->lock after this, so its fine to

		 * Nothing relies on rq->lock after this, so it's fine to

		 * drop it.

		 */

		rq_unpin_lock(rq, &rf);

}

/*

 * IO-wait accounting, and how its mostly bollocks (on SMP).

 * IO-wait accounting, and how it's mostly bollocks (on SMP).

 *

 * The idea behind IO-wait account is to account the idle time that we could

 * have spend running if it were not for IO. That is, if we were to improve the

	/*

	 * Optimization: we know that if all tasks are in the fair class we can

	 * call that function directly, but only if the @prev task wasn't of a

	 * higher scheduling class, because otherwise those loose the

	 * higher scheduling class, because otherwise those lose the

	 * opportunity to pull in more work from other CPUs.

	 */

	if (likely(prev->sched_class <= &fair_sched_class &&

	 * right. rt_mutex_slowunlock()+rt_mutex_postunlock() work together to

	 * ensure a task is de-boosted (pi_task is set to NULL) before the

	 * task is allowed to run again (and can exit). This ensures the pointer

	 * points to a blocked task -- which guaratees the task is present.

	 * points to a blocked task -- which guarantees the task is present.

	 */

	p->pi_top_task = pi_task;

	/*

	 * The RT priorities are set via sched_setscheduler(), but we still

	 * allow the 'normal' nice value to be set - but as expected

	 * it wont have any effect on scheduling until the task is

	 * it won't have any effect on scheduling until the task is

	 * SCHED_DEADLINE, SCHED_FIFO or SCHED_RR:

	 */

	if (task_has_dl_policy(p) || task_has_rt_policy(p)) {

 *

 * The scheduler is at all times free to pick the calling task as the most

 * eligible task to run, if removing the yield() call from your code breaks

 * it, its already broken.

 * it, it's already broken.

 *

 * Typical broken usage is:

 *

#ifdef CONFIG_SMP

	/*

	 * Its possible that init_idle() gets called multiple times on a task,

	 * It's possible that init_idle() gets called multiple times on a task,

	 * in that case do_set_cpus_allowed() will not do the right thing.

	 *

	 * And since this is boot we can forgo the serialization.

			return -EINVAL;

#endif

		/*

		 * Serialize against wake_up_new_task() such that if its

		 * Serialize against wake_up_new_task() such that if it's

		 * running, we're sure to observe its full state.

		 */

		raw_spin_lock_irq(&task->pi_lock);