lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a421b31b-53ad-4f56-88be-66a7d4c3bb61@redhat.com>
Date: Fri, 6 Sep 2024 09:53:15 +0200
From: Jocelyn Falempe <jfalempe@...hat.com>
To: John Ogness <john.ogness@...utronix.de>,
 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, 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 05/09/2024 17:22, John Ogness wrote:
> On 2024-08-01, John Ogness <john.ogness@...utronix.de> wrote:
>> On 2024-08-01, Jocelyn Falempe <jfalempe@...hat.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.

Thanks for the head-up.
I will rebase it on top of Linux-next, and adapt to the new 
write_thread() API, it should be much simpler.


I also need to adapt to the drm client rework 
(https://patchwork.freedesktop.org/series/137391/) so that it will be 
possible to choose on kernel command line between drm_log and fbdev 
emulation/fbcon.

Best regards,

-- 

Jocelyn

> 
> John Ogness
> 


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ