[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <feb72a8c-06c1-48d9-abb0-d680c11922a7@web.de>
Date: Wed, 18 Dec 2024 13:25:17 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Jocelyn Falempe <jfalempe@...hat.com>, dri-devel@...ts.freedesktop.org,
Caleb Connolly <caleb.connolly@...aro.org>, Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...il.com>, "Guilherme G. Piccoli"
<gpiccoli@...lia.com>, Jani Nikula <jani.nikula@...ux.intel.com>,
Javier Martinez Canillas <javierm@...hat.com>,
John Ogness <john.ogness@...utronix.de>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Petr Mladek <pmladek@...e.com>,
Thomas Zimmermann <tzimmermann@...e.de>, bluescreen_avenger@...izon.net
Cc: LKML <linux-kernel@...r.kernel.org>,
Simona Vetter <simona.vetter@...ll.ch>
Subject: Re: [PATCH v9 2/6] drm/log: Introduce a new boot logger to draw the
kmsg on the screen
…
> +++ b/drivers/gpu/drm/clients/drm_log.c
> @@ -0,0 +1,370 @@
…
> +static int drm_log_count_modeset(struct drm_client_dev *client)
> +{
> + struct drm_mode_set *mode_set;
> + int count = 0;
> +
> + mutex_lock(&client->modeset_mutex);
> + drm_client_for_each_modeset(mode_set, client)
> + count++;
> + mutex_unlock(&client->modeset_mutex);
> + return count;
> +}
…
Under which circumstances would you become interested to apply a statement
like “guard(mutex)(&client->modeset_mutex);”?
https://elixir.bootlin.com/linux/v6.13-rc3/source/include/linux/mutex.h#L201
Regards,
Markus
Powered by blists - more mailing lists