mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paul Fulghum <paulkf@microgate.com>
Cc: James Simmons <jsimmons@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [PATCH] Use tty_schedule in VT code.
Date: Wed, 18 Jul 2007 13:08:33 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0707181303070.27353@woody.linux-foundation.org> (raw)
In-Reply-To: <1184783279.3444.15.camel@x2.microgate.com>



On Wed, 18 Jul 2007, Paul Fulghum wrote:
> 
> It might be safest to drop this portion so you can get the
> obvious part of the patch accepted (consolidating
> the redundant xxx_schedule_flip functions).

But wasn't the whole _point_ that con_schedule_flip() potentially gets 
called from interrupt context, and thus that part is wrong. It's why 
con_schedule_flip() was different from tty_schedule_flip() to begin with, 
no?

If a tty driver has marked itself low-latency, it's still wrong to do the 
flush_to_ldisc() from interrupt context if a console event happens in 
interrupt context.

I thought that was the whole *point* of the difference between 
"tty_schedule_flip()" and "con_schedule_flip()", as far as I know. The 
"con_schedule_flip()" can be called from any context (console messages), 
while "tty_schedule_flip()" is only called from well-behaved tty layer.

But I really don't know. I used to be involved with the tty layer, these 
days I'd rather avoid it. This "simple" patch seems to be anything but, 
and I'd like somebody to just make sure that all the issues are taken care 
of.

Alan?

		Linus

  parent reply	other threads:[~2007-07-18 20:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 18:37 James Simmons
2007-07-17 18:49 ` Samuel Thibault
2007-07-17 19:17   ` James Simmons
2007-07-17 20:31     ` Paul Fulghum
2007-07-17 19:24 ` Linus Torvalds
2007-07-17 20:35   ` Paul Fulghum
2007-07-17 19:44     ` Linus Torvalds
2007-07-17 19:52       ` James Simmons
2007-07-17 20:42         ` Linus Torvalds
2007-07-17 23:35           ` Alan Cox
2007-07-18 18:17           ` James Simmons
2007-07-18 18:27             ` Paul Fulghum
2007-07-18 19:57               ` James Simmons
2007-07-18 21:12                 ` Paul Fulghum
2007-07-18 20:08               ` Linus Torvalds [this message]
2007-07-18 21:36                 ` Alan Cox
2007-07-17 21:06         ` Paul Fulghum
2007-07-17 20:15           ` James Simmons
2007-07-17 21:33             ` Paul Fulghum
2007-07-18 17:19               ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2007-05-08 20:10 James Simmons
2007-05-08 20:32 ` Paul Fulghum
2007-05-09 20:58   ` Paul Fulghum
2007-05-09 20:56     ` James Simmons
2007-05-09 23:02       ` Paul Fulghum

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=alpine.LFD.0.999.0707181303070.27353@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    --cc=paulkf@microgate.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®