From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Len Brown <len.brown@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] PM: invoke suspend notifications after console switch
Date: Wed, 23 Jan 2008 16:07:45 +0100 [thread overview]
Message-ID: <200801231607.46112.rjw@sisk.pl> (raw)
In-Reply-To: <20080111182042.GC4016@ucw.cz>
On Friday, 11 of January 2008, Pavel Machek wrote:
> On Thu 2008-01-10 14:14:36, Johannes Berg wrote:
> >
> > On Mon, 2007-12-17 at 02:09 +0100, Johannes Berg wrote:
> > > A subsequent patch will enable apm-emulation notification for suspends
> > > triggered in any way by using the suspend notifications. This causes
> > > the system to lock up between X being needed to switch away from the
> > > VT and X already waiting for resume in the apm ioctl.
> > >
> > > This patch moves the console switch (if enabled) before the suspend
> > > notification (and after the resume notification) to avoid this issue.
> >
> > I don't see this in the suspend git tree yet, anything wrong with it?
>
> 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.
Well, in uswsusp we do the console switch before the suspend notifiers
(although from the user land).
Rafael
next prev parent reply other threads:[~2008-01-23 15:07 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 [this message]
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
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=200801231607.46112.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=johannes@sipsolutions.net \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
/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