lkml.org 
[lkml]   [2017]   [Feb]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock
On Tue, Feb 28, 2017 at 11:59:24AM +0800, Fengguang Wu wrote:
> Hello,
>
> Here is another bisect result with a different call trace.

Is this a single processor VM without pre-emption? It's a busy spin
loop, so relies on the other thread being run to break the loop. That
cpu_relax() should become cond_resched()?
-Chris


--
Chris Wilson, Intel Open Source Technology Centre

\
 
 \ /
  Last update: 2017-02-28 09:56    [W:0.083 / U:0.180 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site