From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751926AbcDRIpJ (ORCPT ); Mon, 18 Apr 2016 04:45:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:53169 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750849AbcDRIpH (ORCPT ); Mon, 18 Apr 2016 04:45:07 -0400 Reply-To: xlpang@redhat.com Subject: Re: [PATCH v3 1/6] rtmutex: Deboost before waking up the top waiter References: <1460633827-345-1-git-send-email-xlpang@redhat.com> <1460633827-345-2-git-send-email-xlpang@redhat.com> To: Thomas Gleixner Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Juri Lelli , Ingo Molnar , Steven Rostedt From: Xunlei Pang Message-ID: <57149E8A.6060701@redhat.com> Date: Mon, 18 Apr 2016 16:44:58 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016/04/18 at 16:23, Thomas Gleixner wrote: > On Thu, 14 Apr 2016, Xunlei Pang wrote: >> We should deboost before waking the high-prio task such that >> we don't run two tasks with the 'same' priority. > No. This is fundamentaly broken. > > T1 (prio 0) lock(X) > > --> preemption > > T2 (prio 10) lock(X) > boost(T1) > schedule() > > T1 (prio 10) unlock(X) We add a preempt_disable() before deboost to avoid the breakage, there's also some comment about this in the patch's code. Regards, Xunlei > deboost() > (prio 0) > > --> preemption > > T3 (prio 5) .... > > Classic priority inversion enabled by a mechanism to avoid it. Brilliant > stuff. > > Thanks, > > tglx