linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Andrew Morton <akpm@osdl.org>,
	James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH] VT locking
Date: Tue, 6 Jan 2004 13:16:36 +0100	[thread overview]
Message-ID: <20040106121636.GA888@elf.ucw.cz> (raw)
In-Reply-To: <1073349182.9504.175.camel@gaston>

Hi!

> The VT code is currently, it seems, full of races, it basically doesn't
> do any locking... This patch is definitely not fixing everything,
> but at

And the races bite, BTW. For years I was seeing weird stuff like
console output on blanked console if scroll happened at approximately
same time as blank. It was hard to reproduce reliably, through.
								Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

  reply	other threads:[~2004-01-06 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06  0:33 [PATCH] VT locking Benjamin Herrenschmidt
2004-01-06 12:16 ` Pavel Machek [this message]
2004-01-06 16:31 ` Geert Uytterhoeven
2004-01-06 21:44   ` Benjamin Herrenschmidt
2004-01-06 22:00     ` Andrew Morton
2004-01-06 23:08       ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2004-01-06  0:17 Benjamin Herrenschmidt

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=20040106121636.GA888@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).