On Wed, Jun 28, 2017 at 5:08 PM, Steven Rostedt wrote:
> On Wed, 28 Jun 2017 12:36:35 +0200
> Daniel Vetter wrote:
>
>> There's a bunch of folks who're trying to make printk less
>> contended and faster, but there's a problem: printk uses the
>> console_lock, and the console lock has become the B
On Wed, Jun 28, 2017 at 1:00 PM, Alan Cox wrote:
> On Wed, 28 Jun 2017 12:36:35 +0200
> Daniel Vetter wrote:
>
>> There's a bunch of folks who're trying to make printk less
>> contended and faster, but there's a problem: printk uses the
>> console_lock, and the console lock has become the BKL for
On Wed, 28 Jun 2017 12:36:35 +0200
Daniel Vetter wrote:
> There's a bunch of folks who're trying to make printk less
> contended and faster, but there's a problem: printk uses the
> console_lock, and the console lock has become the BKL for all things
> fbdev/fbcon, which in turn pulled in half th
There's a bunch of folks who're trying to make printk less
contended and faster, but there's a problem: printk uses the
console_lock, and the console lock has become the BKL for all things
fbdev/fbcon, which in turn pulled in half the drm subsystem under that
lock. That's awkward.
There reasons fo
