From: John Ogness <john.ogness@linutronix.de>
To: Jocelyn Falempe <jfalempe@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Javier Martinez Canillas <javierm@redhat.com>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
bluescreen_avenger@verizon.net, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Date: Thu, 05 Sep 2024 17:28:35 +0206 [thread overview]
Message-ID: <87a5gm2khw.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <87zfpwxqpc.fsf@jogness.linutronix.de>
On 2024-08-01, John Ogness <john.ogness@linutronix.de> wrote:
> On 2024-08-01, Jocelyn Falempe <jfalempe@redhat.com> wrote:
>> I think I can also register one console for each drm driver, which
>> will simplify drm_log even further. (currently it would mean having a
>> circular buffer and work function for each driver which is a bit too
>> much).
>
> Indeed.
>
>> Do you know if there is a chance to have write_thread() in 6.12 or
>> 6.13 ?
FYI: The full NBCON API (with write_thread()) is now available in
linux-next.
It would be great to see a version of drm_log that only implements
write_thread() and does not do any of its own buffering with workqueue
and also does not need to track multiple graphic loggers at the same
time.
John Ogness
next prev parent reply other threads:[~2024-09-05 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 10:04 [RFC PATCH 0/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-08-01 10:04 ` [RFC PATCH 1/3] [NOT FOR REVIEW] drm/panic: Squash of pending series Jocelyn Falempe
2024-08-01 10:04 ` [RFC PATCH 2/3] drm/panic: Move drawing functions to drm_draw Jocelyn Falempe
2024-08-01 10:04 ` [RFC PATCH 3/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-08-01 10:51 ` John Ogness
2024-08-01 13:52 ` Jocelyn Falempe
2024-08-01 14:28 ` John Ogness
2024-09-05 15:22 ` John Ogness [this message]
2024-09-06 7:53 ` Jocelyn Falempe
2024-09-06 8:27 ` John Ogness
2024-09-06 8:47 ` John Ogness
2024-09-06 16:29 ` Jocelyn Falempe
2024-08-01 10:36 ` [RFC PATCH 0/3] " John Ogness
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=87a5gm2khw.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=airlied@gmail.com \
--cc=bluescreen_avenger@verizon.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gpiccoli@igalia.com \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox