From: Johannes Berg <johannes@sipsolutions.net>
To: benh@kernel.crashing.org
Cc: Len Brown <len.brown@intel.com>,
linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] PM: invoke suspend notifications after console switch
Date: Thu, 24 Jan 2008 19:32:11 +0100 [thread overview]
Message-ID: <1201199531.3454.141.camel@johannes.berg> (raw)
In-Reply-To: <1201135592.6815.14.camel@pasglop>
[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]
On Thu, 2008-01-24 at 11:46 +1100, Benjamin Herrenschmidt wrote:
> > Its pretty intrusive I'd say. And it is wrong; we'd prefer userspace
> > to know what we are doing; if they are told we are suspending,
> > userspace may be able to do something more clever than long console
> > switch.
> >
> > I'd prefer this not to go into mainline.
>
> So you'd prefer mainline to be broken and X to lock up ? nice !
>
> The console switch happens -anyway- with the current code right ? So we
> aren't changing that.
Mind you, that's the (only!) other alternative: removing the in-kernel
console switch completely which is the only way to allow userspace to do
something "more clever than long console switch".
> However, (even today I believe), users of /dev/apm_bios, such as X, will
> deadlock the VT subsystem if they get notified of the suspend before the
> kernel initiated console switch happen (which can happen today if the
> suspend is triggered by an APM application I -think- (to be verified)
Yeah I'm pretty sure that can happen, but in fact, that will happen
regardless of this patch until my other patch is applied.
johannes
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2008-01-24 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 1:09 [PATCH] PM: invoke suspend notifications after console switch Johannes Berg
2008-01-10 13:14 ` Johannes Berg
2008-01-10 17:00 ` Rafael J. Wysocki
2008-01-11 18:20 ` Pavel Machek
2008-01-23 15:07 ` Rafael J. Wysocki
2008-01-23 18:03 ` Rafael J. Wysocki
2008-01-25 7:43 ` Pavel Machek
2008-01-24 0:46 ` Benjamin Herrenschmidt
2008-01-24 18:32 ` Johannes Berg [this message]
2008-01-24 8:35 ` Johannes Berg
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=1201199531.3454.141.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=benh@kernel.crashing.org \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.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