From: Ingo Molnar <mingo@elte.hu>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"lkml," <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
John Kacur <jkacur@redhat.com>,
Dinakar Guniguntala <dino@in.ibm.com>,
John Stultz <johnstul@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
Date: Sat, 8 Aug 2009 17:27:56 +0200 [thread overview]
Message-ID: <20090808152756.GH28892@elte.hu> (raw)
In-Reply-To: <4A7B5D46.7080109@us.ibm.com>
* Darren Hart <dvhltc@us.ibm.com> wrote:
> So, I think we're fine with respect to the pi_state ownership! In
> fact I finally managed to catch the lock steal in the requeue loop
> in my tracing, and everything worked fine. Going to go rerun a
> bunch more tests and see if I hit any other issues, if I do, I
> suspect they are unrelated to this.
>
> Thanks for the help in thinking this through.
i've got these queued up:
00235fe: futex: Update woken requeued futex_q lock_ptr
1bbf208: rtmutex: Avoid deadlock in rt_mutex_start_proxy_lock()
should i drop them?
Ingo
next prev parent reply other threads:[~2009-08-08 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 0:01 [RFC][PATCH] fixup pi_state in futex_requeue on lock steal Darren Hart
2009-08-06 16:37 ` Peter Zijlstra
2009-08-06 22:46 ` Darren Hart
2009-08-06 22:53 ` Steven Rostedt
2009-08-07 0:36 ` Darren Hart
2009-08-08 15:27 ` Ingo Molnar [this message]
2009-08-08 23:11 ` Darren Hart
2009-08-06 23:07 ` Darren Hart
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=20090808152756.GH28892@elte.hu \
--to=mingo@elte.hu \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=jkacur@redhat.com \
--cc=johnstul@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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