From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Greg KH <gregkh@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Linus Torvalds <torvalds@osdl.org>,
linux-pm@lists.osdl.org
Subject: Re: [patch] suspend/resume debugging: device filter
Date: Sat, 5 May 2007 11:39:32 +0200 [thread overview]
Message-ID: <200705051139.33008.rjw@sisk.pl> (raw)
In-Reply-To: <20070505092425.GA23125@elte.hu>
On Saturday, 5 May 2007 11:24, Ingo Molnar wrote:
>
> * Greg KH <gregkh@suse.de> wrote:
>
> > Here's a (compile tested only) patch that does this on a per-device
> > basis, which is smaller, and should work just as well as your patch.
> >
> > It creates a new file in the power/ directory for every device called
> > "can_suspend". Write a '0' to it to prevent that device from being
> > suspended.
> >
> > Does this work for you?
>
> yeah, i was able to use this too to debug suspend/resume problems. But
> i've added the check to the resume path too - for example sw-suspend
> does a resume of devices during its suspend cycle, cutting off much of
> the netconsole output.
>
> which makes the can_suspend flag mis-named - perhaps rename it to
> exclude_pm ?
>
> updated patch below, against v2.6.21. Could we get this into v2.6.22
> please? It's a real time-saver.
ACK
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-05 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070125110501.GA25151@elte.hu>
2007-01-26 1:55 ` [patch] suspend/resume debugging: device filter Greg KH
2007-01-26 9:36 ` Pavel Machek
2007-05-05 9:24 ` Ingo Molnar
2007-05-05 9:39 ` Rafael J. Wysocki [this message]
2007-05-05 10:08 ` Pavel Machek
2007-05-08 2:54 ` [linux-pm] " Greg KH
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=200705051139.33008.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mingo@elte.hu \
--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