mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	FrameBuffer List <linux-fbdev@vuser.vu.union.edu>,
	Linux console project  <linuxconsole-dev@lists.source.redhat.com>
Subject: Re: [linux-fbdev] Re: console spin_lock
Date: Wed, 17 Jan 2001 18:02:21 MET-1	[thread overview]
Message-ID: <12D9032A5156@vcnet.vc.cvut.cz> (raw)

On 18 Jan 01 at 0:49, Andrew Morton wrote:

> Assumption:
> - Once the system is up and running, it's always safe to
>   call down() when in_interrupt() returns false - probably
>   not the case in parts of the exit path - tough.
> 
> Anyway, that's the thoughtware.  Sound sane?

Do not forget to handle printk() done by fbdev driver... It
may invoke printk() from user context, but with console_semaphore
already held... Something like reentrant_semaphore? Also, we
should declare which console/fbdev function can printk/can schedule 
and which must not, as using interrupts & schedule could yield
CPU to other tasks when (hardware assisted) operation is performed.
Some of them (clear, bmove) can take loong time to finish.
                                    Best regards,
                                            Petr Vandrovec
                                            vandrove@vc.cvut.cz
                                            
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2001-01-17 17:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=12D9032A5156@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=andrewm@uow.edu.au \
    --cc=linux-fbdev@vuser.vu.union.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.source.redhat.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

all inboxes | Powered by JetHome®