From: Peter Zijlstra <peterz@infradead.org>
To: xlpang@redhat.com
Cc: linux-kernel@vger.kernel.org, Juri Lelli <juri.lelli@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] sched/deadline/rtmutex: Fix a PI crash for deadline tasks
Date: Tue, 5 Apr 2016 13:32:33 +0200 [thread overview]
Message-ID: <20160405113233.GL3448@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <57039806.2070102@redhat.com>
On Tue, Apr 05, 2016 at 06:48:38PM +0800, Xunlei Pang wrote:
> This is cool, I think we should also init "pi_task" properly for INIT_MUTEX and fork,
> otherwise looks good to me :-)
Indeed..
> Besides, do you think we can kill "pi_waiters_leftmost" from task_struct, as we
> can easily get it from "pi_waiters"?
I don't quickly see a way to do that, different locking rules govern the
two.. which was the whole problem we started with :/
> I will test it further with these new changes soon.
Thanks!
next prev parent reply other threads:[~2016-04-05 11:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 11:00 Xunlei Pang
2016-04-01 11:38 ` Peter Zijlstra
2016-04-01 12:23 ` Xunlei Pang
2016-04-01 13:12 ` Peter Zijlstra
2016-04-01 13:34 ` Xunlei Pang
2016-04-01 21:51 ` Peter Zijlstra
2016-04-02 10:19 ` Xunlei Pang
2016-04-05 8:38 ` Xunlei Pang
2016-04-05 9:19 ` Peter Zijlstra
2016-04-05 9:29 ` Peter Zijlstra
2016-04-05 10:48 ` Xunlei Pang
2016-04-05 11:32 ` Peter Zijlstra [this message]
2016-04-08 16:25 ` Steven Rostedt
2016-04-08 17:38 ` Peter Zijlstra
2016-04-08 18:50 ` Steven Rostedt
2016-04-08 18:59 ` Peter Zijlstra
2016-04-08 19:15 ` Steven Rostedt
2016-04-08 19:28 ` Steven Rostedt
2016-04-09 3:27 ` Xunlei Pang
2016-04-09 3:25 ` Xunlei Pang
2016-04-09 13:29 ` Peter Zijlstra
2016-04-10 8:22 ` Xunlei Pang
2016-04-12 3:08 ` Xunlei Pang
2016-04-12 15:51 ` Peter Zijlstra
2016-04-13 2:13 ` Xunlei Pang
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=20160405113233.GL3448@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=xlpang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome