Commit 0e4add4a authored by Hillf Danton's avatar Hillf Danton Committed by Will Deacon

arm64: assembler: Update comment above cond_yield_neon() macro

Since commit 7faa313f ("arm64: preempt: Fix big-endian when checking
preempt count in assembly") both the preempt count and the 'need_resched'
flag are checked as part of a single 64-bit load in cond_yield_neon(),
so update the stale comment to reflect reality.

Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Dave Martin <Dave.Martin@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: default avatarHillf Danton <hdanton@sina.com>
Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
parent 14ae42a6
...@@ -718,12 +718,11 @@ USER(\label, ic ivau, \tmp2) // invalidate I line PoU ...@@ -718,12 +718,11 @@ USER(\label, ic ivau, \tmp2) // invalidate I line PoU
* the output section, any use of such directives is undefined. * the output section, any use of such directives is undefined.
* *
* The yield itself consists of the following: * The yield itself consists of the following:
* - Check whether the preempt count is exactly 1, in which case disabling * - Check whether the preempt count is exactly 1 and a reschedule is also
* preemption once will make the task preemptible. If this is not the case, * needed. If so, calling of preempt_enable() in kernel_neon_end() will
* yielding is pointless. * trigger a reschedule. If it is not the case, yielding is pointless.
* - Check whether TIF_NEED_RESCHED is set, and if so, disable and re-enable * - Disable and re-enable kernel mode NEON, and branch to the yield fixup
* kernel mode NEON (which will trigger a reschedule), and branch to the * code.
* yield fixup code.
* *
* This macro sequence may clobber all CPU state that is not guaranteed by the * This macro sequence may clobber all CPU state that is not guaranteed by the
* AAPCS to be preserved across an ordinary function call. * AAPCS to be preserved across an ordinary function call.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment