From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753391AbbCBDUl (ORCPT ); Sun, 1 Mar 2015 22:20:41 -0500 Received: from mail-wi0-f181.google.com ([209.85.212.181]:44790 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753292AbbCBDUj (ORCPT ); Sun, 1 Mar 2015 22:20:39 -0500 Message-ID: <1425266436.7429.8.camel@gmail.com> Subject: Re: [PATCH 2/3] locking: ww_mutex: Allow to use rt_mutex instead of mutex for the baselock From: Mike Galbraith To: Sebastian Andrzej Siewior Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Maarten Lankhorst Date: Mon, 02 Mar 2015 04:20:36 +0100 In-Reply-To: <1425056229-22326-3-git-send-email-bigeasy@linutronix.de> References: <1425056229-22326-1-git-send-email-bigeasy@linutronix.de> <1425056229-22326-3-git-send-email-bigeasy@linutronix.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2015-02-27 at 17:57 +0100, Sebastian Andrzej Siewior wrote: > This patch makes it possible to replace the base mutex by a rt_mutex. In > general one would not do this. I would argue that the thing should be born as a full fledged primitive, not a config option, as an rt_ww_mutex is the ww extension of rt_mutex. We have to do the global substitution in -rt, but why should it not exist in its own right in mainline? -Mike