Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1589294 > unrolled thread

Re: [locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock Chris Wilson <chris@chris-wilson.co.uk> - 2017-02-28 10:00 +0100

#1589294 — 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

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web