public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm] PM: Remove sleeping from suspend_console
Date: Tue, 5 Sep 2006 08:28:42 +0200	[thread overview]
Message-ID: <20060905062842.GA21738@suse.de> (raw)
In-Reply-To: <200609042250.41592.rjw@sisk.pl>

On Mon, Sep 04, 2006 at 10:50:40PM +0200, Rafael J. Wysocki wrote:
> Remove ssleep() from suspend_console().
> 
> Stefan thinks it is unnecessary and will slow down the suspend too much.

"unnecessary" is not exactly what i think, rather "unacceptable" :-)
We probably need to do something for some kinds of consoles to make sure all
characters are sent, but sleeping unconditionally is not the right thing IMO.

> --- linux-2.6.18-rc5-mm1.orig/kernel/printk.c
> +++ linux-2.6.18-rc5-mm1/kernel/printk.c
> @@ -713,11 +713,6 @@ void suspend_console(void)
>  	printk("Suspending console(s)\n");
>  	acquire_console_sem();
>  	console_suspended = 1;
> -	/* This is needed so that all of the messages that have already been
> -	 * written to all consoles can be actually transmitted (eg. over a
> -	 * network) before we try to suspend the consoles' devices.
> -	 */
> -	ssleep(2);
>  }
>  
>  void resume_console(void)

-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 

  reply	other threads:[~2006-09-05  6:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 20:50 [PATCH -mm] PM: Remove sleeping from suspend_console Rafael J. Wysocki
2006-09-05  6:28 ` Stefan Seyfried [this message]
2006-09-05 11:08   ` Rafael J. Wysocki

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=20060905062842.GA21738@suse.de \
    --to=seife@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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