From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stefan Seyfried <seife@suse.de>
Cc: Pavel Machek <pavel@ucw.cz>,
nigel@nigel.suspend2.net, linux-kernel@vger.kernel.org,
suspend-devel@lists.sourceforge.net,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] get rid of CONFIG_DISABLE_CONSOLE_SUSPEND
Date: Thu, 28 Jun 2007 21:12:44 +0200 [thread overview]
Message-ID: <200706282112.45378.rjw@sisk.pl> (raw)
In-Reply-To: <20070628172514.GA12770@suse.de>
On Thursday, 28 June 2007 19:25, Stefan Seyfried wrote:
> (CC'ing Linus, since disabling consoles during suspend was his idea IIRC)
>
> On Thu, Jun 28, 2007 at 05:34:54PM +0200, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Thursday, 28 June 2007 15:51, Pavel Machek wrote:
> > > Hi!
> > >
> > > What about this? (Only compile tested, but looks pretty obvious to
> > > me). Something like this should get us rid of ugly option, and still
> > > solve debugging problems... Hmmm?
> > > Pavel
> > >
> > > Kill CONFIG_DISABLE_CONSOLE_SUSPEND; it should not be configurable at
> > > all, instead, we should automatically keep console alive when
> > > possible.
> > >
> > > Signed-off-by: Pavel Machek <pavel@suse.cz>
> > >
> > > diff --git a/drivers/char/lp.c b/drivers/char/lp.c
> > > index 62051f8..8267ff8 100644
> > > --- a/drivers/char/lp.c
> > > +++ b/drivers/char/lp.c
> > > @@ -144,7 +144,7 @@ static unsigned int lp_count = 0;
> > > static struct class *lp_class;
> > >
> > > #ifdef CONFIG_LP_CONSOLE
> > > -static struct parport *console_registered; // initially NULL
> > > +static struct parport *console_registered;
> > > #endif /* CONFIG_LP_CONSOLE */
> >
> > Could you please avoid fixing things like this, white space etc. in this patch?
> > It would be easier to read ...
>
> Yes.
>
> > I generally agree with the idea, but the patch needs a clean up, IMHO.
>
> However, we don't know which consoles are safe to stay alive during suspend.
> Generally, defaulting to suspending them all is not a bad idea IMHO.
> And IIRC it is plain luck if a serial console survives the suspend (or was
> the serial code fixed recently?)
Well, I don't think so, but I'm not sure.
The VGA/fb console also should be off during suspend (not necessarily during
hibernation, though). IIRC, that's what caused Linus to introduce the
suspending of consoles after all.
> So i do not care too much, but my / Frank's patch was shorter :-) and safer.
I'm not sure which way to go. On the one hand, I agree that we should rather
fix the consoles so that we know which one is suspend-safe and which is not
and disable the unsafe ones, but on the other hand we are not there yet and it
_sometimes_ is useful not to suspend a console even if we know that it will
break things.
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
next prev parent reply other threads:[~2007-06-28 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 13:51 Pavel Machek
2007-06-28 14:12 ` Tejun Heo
2007-06-28 15:34 ` Rafael J. Wysocki
2007-06-28 17:25 ` Stefan Seyfried
2007-06-28 19:12 ` Rafael J. Wysocki [this message]
2007-06-29 12:36 ` Stefan Seyfried
2007-07-04 19:33 ` Pavel Machek
2007-07-04 21:44 ` Rafael J. Wysocki
2007-07-04 22:39 ` Pavel Machek
2007-07-05 9:38 ` Stefan Seyfried
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=200706282112.45378.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=seife@suse.de \
--cc=suspend-devel@lists.sourceforge.net \
--cc=torvalds@linux-foundation.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
Powered by JetHome