The core_idle_lock_held loops when the lock bit is held by others.
However, it is possible that after the lock bit is cleared, some one
else sees it first and sets the lock bit. And lwarx loads a value with
lock bit set, and the lock bit may be cleared in the following stwcx.
It is possible the first one is still executing in the critical section.
This patch rechecks the lock bit after lwarx, and go back to loop if it
is set.
Signed-off-by: Li Zhong <redacted>
---
arch/powerpc/kernel/idle_book3s.S | 2 ++
1 file changed, 2 insertions(+)
From: Paul Mackerras <hidden> Date: 2016-10-25 04:15:33
On Tue, Oct 25, 2016 at 11:24:34AM +0800, Li Zhong wrote:
The core_idle_lock_held loops when the lock bit is held by others.
However, it is possible that after the lock bit is cleared, some one
else sees it first and sets the lock bit. And lwarx loads a value with
lock bit set, and the lock bit may be cleared in the following stwcx.
It is possible the first one is still executing in the critical section.
This patch rechecks the lock bit after lwarx, and go back to loop if it
is set.
On 25 Oct 2016, at 12:15, Paul Mackerras [off-list ref] wrote:
=20
On Tue, Oct 25, 2016 at 11:24:34AM +0800, Li Zhong wrote:
quoted
The core_idle_lock_held loops when the lock bit is held by others.
However, it is possible that after the lock bit is cleared, some one
else sees it first and sets the lock bit. And lwarx loads a value =
with
quoted
lock bit set, and the lock bit may be cleared in the following stwcx.
It is possible the first one is still executing in the critical =
section.
quoted
=20
This patch rechecks the lock bit after lwarx, and go back to loop if =