From: Peter Zijlstra <peterz@infradead.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Ingo Molnar" <mingo@redhat.com>,
intel-gfx@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mutex: Report recursive ww_mutex locking early
Date: Mon, 30 May 2016 12:27:46 +0200 [thread overview]
Message-ID: <20160530102746.GA3193@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <322ba7ac-909d-bda5-4b1f-73e22cf10c97@linux.intel.com>
On Mon, May 30, 2016 at 11:43:31AM +0200, Maarten Lankhorst wrote:
> Patch not applied, SCHED_RR:
ww_mutex isn't RT aware at all; its one of the things I still have on a
todo list. Should I look harder at finding time for this?
next prev parent reply other threads:[~2016-05-30 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 8:31 [PATCH] mutex: Do not spin/queue before performing ww_mutex deadlock avoidance Chris Wilson
2016-05-26 8:31 ` Chris Wilson
2016-05-26 9:02 ` ✗ Ro.CI.BAT: warning for " Patchwork
2016-05-26 10:37 ` [PATCH] " Maarten Lankhorst
2016-05-26 10:43 ` Chris Wilson
2016-05-26 10:43 ` Chris Wilson
2016-05-26 11:08 ` Maarten Lankhorst
2016-05-26 20:08 ` [PATCH] mutex: Report recursive ww_mutex locking early Chris Wilson
2016-05-26 20:08 ` Chris Wilson
2016-05-30 7:43 ` Maarten Lankhorst
2016-05-30 9:11 ` Peter Zijlstra
2016-05-30 9:11 ` Peter Zijlstra
2016-05-30 9:43 ` Maarten Lankhorst
2016-05-30 9:43 ` Maarten Lankhorst
2016-05-30 10:27 ` Peter Zijlstra [this message]
2016-05-30 10:45 ` Chris Wilson
2016-05-30 11:16 ` Maarten Lankhorst
2016-05-30 11:16 ` Maarten Lankhorst
2016-06-03 10:46 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2016-05-27 5:34 ` ✗ Ro.CI.BAT: warning for mutex: Do not spin/queue before performing ww_mutex deadlock avoidance (rev2) Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160530102746.GA3193@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chris@chris-wilson.co.uk \
--cc=christian.koenig@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.