Messages in this thread | | | Date | Tue, 28 Feb 2017 08:53:33 +0000 | From | Chris Wilson <> | Subject | Re: [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
| |