From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] fbcon: Make fbcon a built-time depency for fbdev
Date: Wed, 28 Jun 2017 11:00:03 +0000 [thread overview]
Message-ID: <20170628120003.6e2f1ef6@alans-desktop> (raw)
In-Reply-To: <20170628103635.24651-1-daniel.vetter@ffwll.ch>
On Wed, 28 Jun 2017 12:36:35 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> 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 the drm subsystem under that
> lock. That's awkward.
Yes - very. Although if you implement your console printing method with
sufficient cunning it shouldn't cause much latency in most cases but for
unaccelerated fb it's really bad.
It also makes it unnecessarily hard for a drm driver to accelerate
console output.
> 4. Push console_lock down the call-chain, until it is down in
> console_register again.
I don't think that's actually going to work out. To fix it is going to
need more invasive changes so that you can 'create' a console and set it
up separately to actually 'enabling' it when you make it visible and
start scribbling. I don't see any other way to make the changeover
locking saner at this point without still having huge potential stalls in
printk().
Reviewed-by: Alan Cox <alan@linux.intel.com>
Alan
next prev parent reply other threads:[~2017-06-28 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 10:36 [PATCH] fbcon: Make fbcon a built-time depency for fbdev Daniel Vetter
2017-06-28 11:00 ` Alan Cox [this message]
2017-06-28 11:48 ` Daniel Vetter
[not found] ` <20170628110819.70eb0ce0@gandalf.local.home>
2017-06-28 15:55 ` Daniel Vetter
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=20170628120003.6e2f1ef6@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).