Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030226AbWJXJo5 (ORCPT ); Tue, 24 Oct 2006 05:44:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030230AbWJXJo5 (ORCPT ); Tue, 24 Oct 2006 05:44:57 -0400 Received: from www.osadl.org ([213.239.205.134]:33154 "EHLO mail.tglx.de") by vger.kernel.org with ESMTP id S1030226AbWJXJo4 (ORCPT ); Tue, 24 Oct 2006 05:44:56 -0400 Subject: Re: rtmutex's wait_lock in 2.6.18-rt7 From: Thomas Gleixner Reply-To: tglx@linutronix.de To: Esben Nielsen Cc: Ingo Molnar , linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Date: Tue, 24 Oct 2006 11:46:03 +0200 Message-Id: <1161683163.22373.68.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 763 Lines: 21 On Mon, 2006-10-23 at 11:55 +0200, Esben Nielsen wrote: > Hi, > I see that in 2.6.18-rt7 the rtmutex's wait_lock is sudden interrupt > disabling. I don't see the need as no (hard) interrupt-handlers should be > touching any mutex. It does not touch mutexes, but the dynamic priority adjustment of the hrtimer softirq needs it. The correct solution will be moving the timer callback into the process context, as it will be woken up anyway, but that's more complex to do than it looks in the first place. tglx - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/