From: Tejun Heo <tj@kernel.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
pavel@ucw.cz, lenb@kernel.org, ak@linux.intel.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3] PM/Memory-hotplug: Avoid task freezing failures
Date: Mon, 21 Nov 2011 08:40:06 -0800 [thread overview]
Message-ID: <20111121164006.GB15314@google.com> (raw)
In-Reply-To: <4EC9D557.9090008@linux.vnet.ibm.com>
Hello, Srivatsa.
On Mon, Nov 21, 2011 at 10:06:39AM +0530, Srivatsa S. Bhat wrote:
> void lock_system_sleep(void)
> {
> /* simplified freezer_do_not_count() */
> current->flags |= PF_FREEZER_SKIP;
>
> mutex_lock(&pm_mutex);
>
> }
>
> void unlock_system_sleep(void)
> {
> mutex_unlock(&pm_mutex);
>
> /* simplified freezer_count() */
> current->flags &= ~PF_FREEZER_SKIP;
>
> }
>
> We probably don't want the restriction that freezer_do_not_count() and
> freezer_count() work only for userspace tasks. So I have open coded
> the relevant parts of those functions here.
>
> I haven't tested this solution yet. Let me know if this solution looks
> good and I'll send it out as a patch after testing and analyzing some
> corner cases, if any.
Ooh ooh, I definitely like this one much better. Oleg did something
similar w/ wait_event_freezekillable() too. On related notes,
* I think it would be better to remove direct access to pm_mutex and
use [un]lock_system_sleep() universally. I don't think hinging it
on CONFIG_HIBERNATE_CALLBACKS buys us anything.
* In the longer term, we should be able to toggle PF_NOFREEZE instead
as SKIP doesn't mean anything different. We'll probably need a
better API tho. But for now SKIP should work fine.
Thank you.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-21 16:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 8:30 Srivatsa S. Bhat
2011-11-19 18:32 ` Tejun Heo
2011-11-19 19:35 ` Srivatsa S. Bhat
2011-11-19 21:57 ` Rafael J. Wysocki
2011-11-20 6:03 ` Srivatsa S. Bhat
2011-11-20 10:24 ` Rafael J. Wysocki
2011-11-21 4:36 ` Srivatsa S. Bhat
2011-11-21 7:55 ` Chen Gong
2011-11-21 8:22 ` Srivatsa S. Bhat
2011-11-21 16:40 ` Tejun Heo [this message]
2011-11-21 17:04 ` Srivatsa S. Bhat
2011-11-21 17:52 ` Tejun Heo
2011-11-21 18:01 ` Srivatsa S. Bhat
2011-11-21 20:05 ` Rafael J. Wysocki
2011-11-21 18:12 ` [PATCH v4] PM / Memory-hotplug: " Srivatsa S. Bhat
2011-11-21 18:23 ` Tejun Heo
2011-11-21 18:25 ` Srivatsa S. Bhat
2011-11-21 22:41 ` Rafael J. Wysocki
2011-11-21 16:47 ` [PATCH v3] PM/Memory-hotplug: " Tejun Heo
2011-11-21 17:12 ` Srivatsa S. Bhat
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=20111121164006.GB15314@google.com \
--to=tj@kernel.org \
--cc=ak@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
/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