Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1589294
| From | Chris Wilson <chris@chris-wilson.co.uk> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock |
| Date | 2017-02-28 10:00 +0100 |
| Message-ID | <tfLNA-22y-9@gated-at.bofh.it> (permalink) |
| References | <tfHqx-7zd-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock Chris Wilson <chris@chris-wilson.co.uk> - 2017-02-28 10:00 +0100
csiph-web