[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171887359115.3857922.3484081720728678081.b4-ty@kernel.org>
Date: Thu, 20 Jun 2024 10:53:11 +0200
From: Maxime Ripard <mripard@...nel.org>
To: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Amaranath Somalapuram <Amaranath.Somalapuram@....com>,
Andi Shyti <andi.shyti@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Boqun Feng <boqun.feng@...il.com>,
Christian Koenig <christian.koenig@....com>,
Daniel Vetter <daniel@...ll.ch>, David Airlie <airlied@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Huang Rui <ray.huang@....com>, Ingo Molnar <mingo@...hat.com>,
Karolina Stolarek <karolina.stolarek@...el.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>, Thomas Gleixner <tglx@...utronix.de>,
Thomas Zimmermann <tzimmermann@...e.de>, Waiman Long <longman@...hat.com>,
Will Deacon <will@...nel.org>
Subject: Re: (subset) [PATCH REPOST^2] drm/ttm/tests: Let ttm_bo_test
consider different ww_mutex implementation.
On Wed, 19 Jun 2024 16:46:30 +0200, Sebastian Andrzej Siewior wrote:
> PREEMPT_RT has a different locking implementation for ww_mutex. The
> base mutex of struct ww_mutex is declared as struct WW_MUTEX_BASE. The
> latter is defined as `mutex' for non-PREEMPT_RT builds and `rt_mutex'
> for PREEMPT_RT builds.
>
> Using mutex_lock() directly on the base mutex in
> ttm_bo_reserve_deadlock() leads to compile error on PREEMPT_RT.
>
> [...]
Applied to misc/kernel.git (drm-misc-next).
Thanks!
Maxime
Powered by blists - more mailing lists