From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: fli24 <fei.li@intel.com>
Cc: <rjw@sisk.pl>, <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<chuansheng.liu@intel.com>
Subject: Re: [PATCH V3] suspend: enable freeze timeout configuration through sys
Date: Thu, 31 Jan 2013 16:29:32 +0900 [thread overview]
Message-ID: <510A1D5C.90705@jp.fujitsu.com> (raw)
In-Reply-To: <1359608132.7918.2.camel@fli24-HP-Compaq-8100-Elite-CMT-PC>
2013/01/31 13:55, fli24 wrote:
>
> At present, the value of timeout for freezing is 20s, which is
> meaningless in case that one thread is frozen with mutex locked
> and another thread is trying to lock the mutex, as this time of
> freezing will fail unavoidably.
> And if there is no new wakeup event registered, the system will
> waste at most 20s for such meaningless trying of freezing.
>
> With this patch, the value of timeout can be configured to smaller
> value, so such meaningless trying of freezing will be aborted in
> earlier time, and later freezing can be also triggered in earlier
> time. And more power will be saved.
> In normal case on mobile phone, it costs real little time to freeze
> processes. On some platform, it only costs about 20ms to freeze
> user space processes and 10ms to freeze kernel freezable threads.
>
> Signed-off-by: Liu Chuansheng <chuansheng.liu@intel.com>
> Signed-off-by: Li Fei <fei.li@intel.com>
> ---
> Documentation/power/freezing-of-tasks.txt | 5 +++++
> include/linux/freezer.h | 5 +++++
> kernel/power/main.c | 27 +++++++++++++++++++++++++++
> kernel/power/process.c | 4 ++--
> 4 files changed, 39 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/power/freezing-of-tasks.txt b/Documentation/power/freezing-of-tasks.txt
> index 6ec291e..85894d8 100644
> --- a/Documentation/power/freezing-of-tasks.txt
> +++ b/Documentation/power/freezing-of-tasks.txt
> @@ -223,3 +223,8 @@ since they ask the freezer to skip freezing this task, since it is anyway
> only after the entire suspend/hibernation sequence is complete.
> So, to summarize, use [un]lock_system_sleep() instead of directly using
> mutex_[un]lock(&pm_mutex). That would prevent freezing failures.
> +
> +V. Miscellaneous
> +/sys/power/pm_freeze_timeout controls how long it will cost at most to freeze
> +all user space processes or all freezable kernel threads, in unit of millisecond.
> +The default value is 20000, with range of unsigned integer.
> diff --git a/include/linux/freezer.h b/include/linux/freezer.h
> index e4238ce..5a24a33 100644
> --- a/include/linux/freezer.h
> +++ b/include/linux/freezer.h
> @@ -13,6 +13,11 @@ extern bool pm_freezing; /* PM freezing in effect */
> extern bool pm_nosig_freezing; /* PM nosig freezing in effect */
>
> /*
> + * Timeout for stopping processes
> + */
> +extern unsigned int sys_freeze_process_timeout_msecs;
> +
> +/*
> * Check if a process has been frozen
> */
> static inline bool frozen(struct task_struct *p)
> diff --git a/kernel/power/main.c b/kernel/power/main.c
> index 1c16f91..453ead1 100644
> --- a/kernel/power/main.c
> +++ b/kernel/power/main.c
> @@ -553,6 +553,30 @@ power_attr(pm_trace_dev_match);
>
> #endif /* CONFIG_PM_TRACE */
>
> +#ifdef CONFIG_FREEZER
> +static ssize_t pm_freeze_timeout_show(struct kobject *kobj,
> + struct kobj_attribute *attr, char *buf)
> +{
> + return sprintf(buf, "%u\n", sys_freeze_process_timeout_msecs);
> +}
> +
> +static ssize_t pm_freeze_timeout_store(struct kobject *kobj,
> + struct kobj_attribute *attr,
> + const char *buf, size_t n)
> +{
> + unsigned long val;
> +
> + if (kstrtoul(buf, 10, &val))
> + return -EINVAL;
> +
> + sys_freeze_process_timeout_msecs = val;
> + return n;
> +}
> +
> +power_attr(pm_freeze_timeout);
> +
> +#endif /* CONFIG_FREEZER*/
> +
> static struct attribute * g[] = {
> &state_attr.attr,
> #ifdef CONFIG_PM_TRACE
> @@ -576,6 +600,9 @@ static struct attribute * g[] = {
> &pm_print_times_attr.attr,
> #endif
> #endif
> +#ifdef CONFIG_FREEZER
> + &pm_freeze_timeout_attr.attr,
> +#endif
> NULL,
> };
>
> diff --git a/kernel/power/process.c b/kernel/power/process.c
> index d5a258b..ba45a26 100644
> --- a/kernel/power/process.c
> +++ b/kernel/power/process.c
> @@ -21,7 +21,7 @@
> /*
> * Timeout for stopping processes
> */
> -#define TIMEOUT (20 * HZ)
> +unsigned int __read_mostly sys_freeze_process_timeout_msecs = 20000;
20000 does not mean 20 seconds since we can select HZ other than 1000.
So (20 * HZ) is better than 20000.
Thanks,
Yasuaki Ishimatsu
>
> static int try_to_freeze_tasks(bool user_only)
> {
> @@ -36,7 +36,7 @@ static int try_to_freeze_tasks(bool user_only)
>
> do_gettimeofday(&start);
>
> - end_time = jiffies + TIMEOUT;
> + end_time = jiffies + msecs_to_jiffies(sys_freeze_process_timeout_msecs);
>
> if (!user_only)
> freeze_workqueues_begin();
>
next prev parent reply other threads:[~2013-01-31 7:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 2:58 [PATCH] suspend: enable freeze timeout configuration through sysctl fli24
2013-01-29 11:42 ` Rafael J. Wysocki
2013-01-30 6:22 ` Li, Fei
2013-01-30 0:36 ` Andrew Morton
2013-01-30 6:23 ` Li, Fei
2013-01-30 6:23 ` [PATCH V2] suspend: enable freeze timeout configuration through sys fli24
2013-01-30 13:09 ` Rafael J. Wysocki
2013-01-31 5:00 ` Li, Fei
2013-01-31 4:55 ` [PATCH V3] " fli24
2013-01-31 7:29 ` Yasuaki Ishimatsu [this message]
2013-01-31 9:13 ` Li, Fei
2013-01-31 9:52 ` anish singh
2013-01-31 22:29 ` Rafael J. Wysocki
2013-02-01 1:33 ` Li, Fei
2013-02-01 1:56 ` Yasuaki Ishimatsu
2013-02-01 2:02 ` Liu, Chuansheng
2013-02-01 8:56 ` [PATCH V4] " fli24
2013-02-03 13:41 ` Rafael J. Wysocki
2013-02-04 3:08 ` Li, Fei
2013-02-04 3:15 ` Alan Stern
2013-02-04 4:32 ` Liu, Chuansheng
2013-02-04 12:22 ` Rafael J. Wysocki
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=510A1D5C.90705@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=chuansheng.liu@intel.com \
--cc=fei.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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