From: "Barry K. Nathan" <barryn@pobox.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Barry K. Nathan" <barryn@pobox.com>,
lindqvist@netstar.se, edi@gmx.de, john@hjsoft.com,
linux-kernel@vger.kernel.org, akpm@osdl.org, torvalds@osdl.org
Subject: Re: [PATCH] swsusp: properly suspend and resume *all* devices
Date: Mon, 3 Jan 2005 21:15:30 -0800 [thread overview]
Message-ID: <20050104051529.GA4465@ip68-4-98-123.oc.oc.cox.net> (raw)
In-Reply-To: <20050103183317.GA1353@elf.ucw.cz>
On Mon, Jan 03, 2005 at 07:33:18PM +0100, Pavel Machek wrote:
> > Ack. [I have similar patch in my tree, but yours is better in error
> > checking area. Please push it to akpm.]
>
> Actually you missed second half: same code should be added around
> swsusp_arch_resume. It is not too critical there, but its right thing
> to do.
Hmmm... I'm not sure how necessary it is, and I think it slows down
resume a tiny bit. However, the more I think about it the more correct it
seems, so here's the follow-up patch. (Andrew, even if this patch is
rejected, please commit my first one to the next -mm release. That patch
alone is still an improvement over the current code.)
Signed-off-by: Barry K. Nathan <barryn@pobox.com>
--- linux-2.6.10-mm1-bkn3/kernel/power/swsusp.c 2005-01-03 06:27:07.753344731 -0800
+++ linux-2.6.10-mm1-bkn4/kernel/power/swsusp.c 2005-01-03 20:19:06.737439106 -0800
@@ -878,6 +878,7 @@
{
int error;
local_irq_disable();
+ device_power_down(PM_SUSPEND_DISK);
/* We'll ignore saved state, but this gets preempt count (etc) right */
save_processor_state();
error = swsusp_arch_resume();
@@ -887,6 +888,7 @@
BUG_ON(!error);
restore_processor_state();
restore_highmem();
+ device_power_up();
local_irq_enable();
return error;
}
next prev parent reply other threads:[~2005-01-04 5:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 14:47 2.6.10: e100 network broken after swsusp/resume John M Flinchbaugh
2004-12-28 21:25 ` Håkan Lindqvist
2005-01-01 23:41 ` Eduard Bloch
2005-01-01 17:23 ` Pavel Machek
2005-01-01 22:17 ` John M Flinchbaugh
2005-01-01 22:52 ` Pavel Machek
2005-01-01 23:14 ` Matthew Garrett
2005-01-02 3:46 ` Barry K. Nathan
2005-01-02 5:57 ` Barry K. Nathan
2005-01-02 18:42 ` John M Flinchbaugh
2005-01-02 20:09 ` Håkan Lindqvist
2005-01-03 5:10 ` Barry K. Nathan
2005-01-03 8:31 ` Barry K. Nathan
2005-01-03 8:53 ` Pavel Machek
2005-01-03 8:47 ` Pavel Machek
2005-01-03 10:14 ` Barry K. Nathan
2005-01-03 15:05 ` [PATCH] swsusp: properly suspend and resume *all* devices Barry K. Nathan
2005-01-03 17:08 ` Pavel Machek
2005-01-03 18:33 ` Pavel Machek
2005-01-04 5:15 ` Barry K. Nathan [this message]
2005-01-04 5:18 ` Barry K. Nathan
2005-01-04 8:44 ` Martin Lucina
2005-01-04 10:30 ` 2.6.10 suspend/resume bustage (was Re: [PATCH] swsusp: properly suspend and resume *all* devices) Martin Lucina
2005-01-04 21:43 ` [PATCH] swsusp: properly suspend and resume *all* devices Pavel Machek
2005-01-05 15:57 ` Lion Vollnhals
2005-01-06 22:29 ` Pavel Machek
2005-01-07 13:47 ` Takashi Iwai
2005-01-07 13:54 ` Pavel Machek
2005-01-07 14:48 ` Dmitry Torokhov
2005-01-07 15:35 ` Vojtech Pavlik
2005-01-07 15:59 ` Lion Vollnhals
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=20050104051529.GA4465@ip68-4-98-123.oc.oc.cox.net \
--to=barryn@pobox.com \
--cc=akpm@osdl.org \
--cc=edi@gmx.de \
--cc=john@hjsoft.com \
--cc=lindqvist@netstar.se \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@osdl.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).