From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alex Goins <agoins@nvidia.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH RT] Align rt_mutex inlining with upstream behavior
Date: Thu, 26 Jan 2017 18:01:09 +0100 [thread overview]
Message-ID: <20170126170109.6zhoohgodtvxot54@linutronix.de> (raw)
In-Reply-To: <1485312350-1265-1-git-send-email-agoins@nvidia.com>
On 2017-01-24 18:45:50 [-0800], Alex Goins wrote:
> mutex_destroy is no-op inline when DEBUG_MUTEX is not enabled. The RT Linux
> patches replace mutex_destroy() with rt_mutex_destroy(). This patch aligns
> rt_mutex_destroy() with mutex_destroy() by using the same no-op inline
> technique.
>
> Signed-off-by: Alex Goins <agoins@nvidia.com>
> Reviewed-by: Andy Ritger <aritger@nvidia.com>
So what is the problem? Why are we doing this? There is still a check to
see if the lock is in use which is also done for the case where
DEBUG_MUTEX is disabled.
Sebastian
next prev parent reply other threads:[~2017-01-26 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 2:45 [PATCH RT] Align rt_mutex inlining with upstream behavior Alex Goins
2017-01-26 17:01 ` Sebastian Andrzej Siewior [this message]
2017-01-30 17:35 ` Andy Ritger
2017-02-03 15:54 ` Sebastian Andrzej Siewior
2017-02-03 16:49 ` Andy Ritger
2017-02-10 17:50 ` Sebastian Andrzej Siewior
2017-02-10 18:09 ` Andy Ritger
2017-02-10 18:28 ` Sebastian Andrzej Siewior
2017-02-10 19:17 ` Alex Goins
2017-02-11 17:52 ` Ingo Molnar
2017-02-11 20:15 ` Thomas Gleixner
2017-02-13 11:20 ` Peter Zijlstra
2017-02-13 13:04 ` Sebastian Andrzej Siewior
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=20170126170109.6zhoohgodtvxot54@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=agoins@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).