mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: John Stultz <jstultz@google.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Joel Fernandes <joelaf@google.com>,
	Qais Yousef <qyousef@google.com>, Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Valentin Schneider <vschneid@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>,
	Zimuzo Ezeozue <zezeozue@google.com>,
	Youssef Esmat <youssefesmat@google.com>,
	Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	"Paul E . McKenney" <paulmck@kernel.org>,
	kernel-team@android.com, Connor O'Brien <connoro@google.com>
Subject: Re: [PATCH v4 02/13] locking/ww_mutex: Remove wakeups from under mutex::wait_lock
Date: Fri, 23 Jun 2023 14:21:16 +0200	[thread overview]
Message-ID: <509d5ee4-45ec-1279-97da-a308ec7f51aa@arm.com> (raw)
In-Reply-To: <20230601055846.2349566-3-jstultz@google.com>

Hi John,

On 01/06/2023 07:58, John Stultz wrote:
> From: Peter Zijlstra <peterz@infradead.org>
> 
> In preparation to nest mutex::wait_lock under rq::lock we need to remove
> wakeups from under it.

[...]

> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Signed-off-by: Connor O'Brien <connoro@google.com>
> Signed-off-by: John Stultz <jstultz@google.com>
> ---
> v2:
> * Move wake_q_init() as suggested by Waiman Long
> ---
>  include/linux/ww_mutex.h  |  3 +++
>  kernel/locking/mutex.c    |  8 ++++++++
>  kernel/locking/ww_mutex.h | 10 ++++++++--
>  3 files changed, 19 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h
> index bb763085479a..9335b2202017 100644
> --- a/include/linux/ww_mutex.h
> +++ b/include/linux/ww_mutex.h
> @@ -19,6 +19,7 @@
>  
>  #include <linux/mutex.h>
>  #include <linux/rtmutex.h>
> +#include <linux/sched/wake_q.h>
>  
>  #if defined(CONFIG_DEBUG_MUTEXES) || \
>     (defined(CONFIG_PREEMPT_RT) && defined(CONFIG_DEBUG_RT_MUTEXES))
> @@ -58,6 +59,7 @@ struct ww_acquire_ctx {
>  	unsigned int acquired;
>  	unsigned short wounded;
>  	unsigned short is_wait_die;
> +	struct wake_q_head wake_q;

you told me that there is already an issue in this patch even w/o PE
when running `insmod /lib/modules/test-ww_mutex.ko`.

The issue is related to Connor's version (1):

https://lkml.kernel.org/r/20221003214501.2050087-2-connoro@google.com

  struct ww_acquire_ctx {

	  struct wake_q_head wake_q;


  __mutex_lock_common()

    if (ww_ctx)
        ww_ctx_wake(ww_ctx)

          wake_up_q(&ww_ctx->wake_q);
          wake_q_init(&ww_ctx->wake_q);


Juri's version (2):

https://lkml.kernel.org/r/20181009092434.26221-3-juri.lelli@redhat.com

  __mutex_lock_common()

      DEFINE_WAKE_Q(wake_q) <-- !!!

      __ww_mutex_check_waiters(..., wake_q)

        __ww_mutex_die(..., wake_q)

          wake_q_add(wake_q, waiter->task)

      wake_up_q(&wake_q)


`insmod /lib/modules/test-ww_mutex.ko` runs fine with (2) but not with
(1) (both w/o the remaining PE patches).

So to test the PE issues we talked about already which come with `[PATCH
v4 09/13] sched: Add proxy execution` and CONFIG_PROXY_EXEC=y we need to
fix (1) or go back to (2).

I haven't found any clues why (2) was changed to (1) so far.

[...]

  reply	other threads:[~2023-06-23 12:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  5:58 [PATCH v4 00/13] Generalized Priority Inheritance via Proxy Execution v3 John Stultz
2023-06-01  5:58 ` [PATCH v4 01/13] sched: Unify runtime accounting across classes John Stultz
2023-06-01  5:58 ` [PATCH v4 02/13] locking/ww_mutex: Remove wakeups from under mutex::wait_lock John Stultz
2023-06-23 12:21   ` Dietmar Eggemann [this message]
2023-06-24  0:41     ` John Stultz
2023-06-01  5:58 ` [PATCH v4 03/13] locking/mutex: make mutex::wait_lock irq safe John Stultz
2023-06-01  5:58 ` [PATCH v4 04/13] locking/mutex: Rework task_struct::blocked_on John Stultz
2023-06-01  5:58 ` [PATCH v4 05/13] locking/mutex: Add task_struct::blocked_lock to serialize changes to the blocked_on state John Stultz
2023-06-01  5:58 ` [PATCH v4 06/13] locking/mutex: Expose __mutex_owner() John Stultz
2023-06-01  5:58 ` [PATCH v4 07/13] sched: Split scheduler execution context John Stultz
2023-06-13 17:12   ` Dietmar Eggemann
2023-06-13 20:37     ` John Stultz
2023-06-01  5:58 ` [PATCH v4 08/13] sched: Unnest ttwu_runnable in prep for proxy-execution John Stultz
2023-06-01  5:58 ` [PATCH v4 09/13] sched: Add proxy execution John Stultz
2023-06-01  5:58 ` [PATCH v4 10/13] sched/rt: Fix proxy/current (push,pull)ability John Stultz
2023-06-01  5:58 ` [PATCH v4 11/13] sched: Fix runtime accounting w/ proxy-execution John Stultz
2023-06-01  5:58 ` [PATCH v4 12/13] sched: Attempt to fix rt/dl load balancing via chain level balance John Stultz
2023-06-01 14:18   ` kernel test robot
2023-06-01 14:33   ` kernel test robot
2023-06-01 14:33   ` kernel test robot
2023-06-01  5:58 ` [PATCH v4 13/13] sched: Fixups to find_exec_ctx John Stultz
2023-06-12 17:21 ` [PATCH v4 00/13] Generalized Priority Inheritance via Proxy Execution v3 K Prateek Nayak
2023-06-12 18:52   ` John Stultz
2023-06-13  3:11     ` K Prateek Nayak
2023-06-13 17:36 ` Dietmar Eggemann
2023-06-13 21:31   ` John Stultz

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=509d5ee4-45ec-1279-97da-a308ec7f51aa@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=boqun.feng@gmail.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=connoro@google.com \
    --cc=joelaf@google.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=qyousef@google.com \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=will@kernel.org \
    --cc=youssefesmat@google.com \
    --cc=zezeozue@google.com \
    /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

Powered by JetHome