[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87plphcgo2.fsf@jogness.linutronix.de>
Date: Fri, 06 Sep 2024 10:53:25 +0206
From: John Ogness <john.ogness@...utronix.de>
To: Jocelyn Falempe <jfalempe@...hat.com>, Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>, Javier Martinez Canillas
<javierm@...hat.com>, "Guilherme G . Piccoli" <gpiccoli@...lia.com>,
bluescreen_avenger@...izon.net, Petr Mladek <pmladek@...e.com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 3/3] drm/log: Introduce a new boot logger to draw
the kmsg on the screen
On 2024-09-06, John Ogness <john.ogness@...utronix.de> wrote:
> Your device_lock()/device_unlock() callbacks probably just need to
> lock/unlock your mutex @drm_log_lock.
Sorry, forgot to mention that the device_lock() callback must also
disable migration. Since you are using a mutex, you will need to
manually do that as well...
mutex_lock(&drm_log_lock);
migrate_disable();
John
Powered by blists - more mailing lists