From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261547AbVFBA3Y (ORCPT ); Wed, 1 Jun 2005 20:29:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261549AbVFBA0k (ORCPT ); Wed, 1 Jun 2005 20:26:40 -0400 Received: from gateway-1237.mvista.com ([12.44.186.158]:41717 "EHLO av.mvista.com") by vger.kernel.org with ESMTP id S261547AbVFBA0L (ORCPT ); Wed, 1 Jun 2005 20:26:11 -0400 Subject: RE: [PATCH] Abstracted Priority Inheritance for RT From: Daniel Walker Reply-To: dwalker@mvista.com To: "Perez-Gonzalez, Inaky" Cc: Esben Nielsen , Ingo Molnar , linux-kernel@vger.kernel.org, sdietrich@mvista.com, rostedt@goodmis.org In-Reply-To: References: Content-Type: text/plain Organization: MontaVista Date: Wed, 01 Jun 2005 17:25:53 -0700 Message-Id: <1117671953.7646.14.camel@dhcp153.mvista.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2005-06-01 at 17:10 -0700, Perez-Gonzalez, Inaky wrote: > Maybe he is referring to the case? > > A owns M > B owns N and is waiting for M > A is trying to wait for N > > These deadlocking cases can be tricky during PI. The bulk of the code is from the current RT mutex, so I'm assuming it handles this case correctly. However, the rt mutex isn't in userspace , so task A or B was a user space task , then the problem would need to be explored.. How does PI change if A or B are user space tasks? Daniel