[Skiboot] [PATCH] Don't detect lock timeouts when timebase is invalid

Stewart Smith stewart at linux.vnet.ibm.com
Tue Mar 13 15:35:38 AEDT 2018

Stewart Smith <stewart at linux.vnet.ibm.com> writes:
> We can have threads waiting on hmi_lock who have an
> invalid timebase. Because of this, we want to go poke
> the register directly rather than rely on
> this_cpu()->tb_invalid (which won't have been set yet).
> Without this patch, you get something like this when
> you're injecting timebase errors:
> [10976.202052846,4] WARNING: Lock has been spinning for 10976394ms
> Fixes: 84186ef0944c9413262f0974ddab3fb1343ccfe8
> Signed-off-by: Stewart Smith <stewart at linux.vnet.ibm.com>
> ---
>  core/lock.c | 7 +++++++
>  1 file changed, 7 insertions(+)

Merged to master as of a8e6cc3f47525f86ef1d69d69a477b6264d0f8ee
Stewart Smith
OPAL Architect, IBM.

More information about the Skiboot mailing list