All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
	"open list:LOCKING PRIMITIVES" <linux-kernel@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Sebastian Siewior <bigeasy@linutronix.de>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Juri Lelli <juri.lelli@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2 2/3] rtmutex: update rt-mutex
Date: Tue, 20 Jun 2017 08:24:31 +0800	[thread overview]
Message-ID: <e98b7dd7-049e-a2fc-d7b2-e8c59e5f3d3e@linaro.org> (raw)
In-Reply-To: <1495689995-29849-2-git-send-email-alex.shi@linaro.org>

Any more comments or concern on this?

Thanks!

On 05/25/2017 01:26 PM, Alex Shi wrote:
> The rtmutex remove a pending owner bit in in rt_mutex::owner, in
> commit 8161239a8bcc ("rtmutex: Simplify PI algorithm and make highest prio task get lock")
> But the document was changed accordingly. Updating it to a meaningful
> state.
> 
> BTW, as 'Steven Rostedt' mentioned:
> There is still technically a "Pending Owner", it's just not called
> that anymore. The pending owner happens to be the top_waiter of a lock
> that has no owner and has been woken up to grab the lock.
> 
> Signed-off-by: Alex Shi <alex.shi@linaro.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Sebastian Siewior <bigeasy@linutronix.de>
> Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
> Cc: Juri Lelli <juri.lelli@arm.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> To: linux-doc@vger.kernel.org
> To: linux-kernel@vger.kernel.org
> To: Jonathan Corbet <corbet@lwn.net>
> To: Ingo Molnar <mingo@redhat.com>
> To: Peter Zijlstra <peterz@infradead.org>
> ---
>  Documentation/locking/rt-mutex.txt | 58 +++++++++++++++++---------------------
>  1 file changed, 26 insertions(+), 32 deletions(-)

  reply	other threads:[~2017-06-20  0:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  5:26 [PATCH v3 1/3] rtmutex: update rt-mutex-design Alex Shi
2017-05-25  5:26 ` [PATCH v2 2/3] rtmutex: update rt-mutex Alex Shi
2017-06-20  0:24   ` Alex Shi [this message]
2017-05-25  5:26 ` [PATCH 3/3] rtmutex: remove unnecessary adjust prio Alex Shi
2017-06-20  0:40   ` Alex Shi
2017-06-01  8:38 ` [PATCH v3 1/3] rtmutex: update rt-mutex-design Alex Shi
2017-06-16  3:16 ` Alex Shi
2017-06-20  0:22 ` Alex Shi
2017-06-20 13:41   ` Steven Rostedt
2017-07-03 18:49 ` Steven Rostedt
2017-07-06  2:39   ` Alex Shi
2017-07-06 13:25     ` Steven Rostedt
2017-07-07  2:39       ` Alex Shi
  -- strict thread matches above, loose matches on Subject: below --
2017-07-07  2:52 [PATCH v4 " Alex Shi
2017-07-07  2:52 ` [PATCH v2 2/3] rtmutex: update rt-mutex Alex Shi
2017-07-11 14:37   ` Alex Shi
2017-04-21 14:12 [PATCH v2 1/3] rtmutex: update rt-mutex-design Alex Shi
2017-04-21 14:12 ` [PATCH v2 2/3] rtmutex: update rt-mutex Alex Shi

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=e98b7dd7-049e-a2fc-d7b2-e8c59e5f3d3e@linaro.org \
    --to=alex.shi@linaro.org \
    --cc=bigeasy@linutronix.de \
    --cc=corbet@lwn.net \
    --cc=juri.lelli@arm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.