From: Wang Qing <wangqing@vivo.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>, Wang Qing <wangqing@vivo.com>,
Santosh Sivaraj <santosh@fossix.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH RFC 0/2] hrtimer: watchdog: support hrtimer suspend when CPU suspend
Date: Tue, 22 Jun 2021 17:06:45 +0800 [thread overview]
Message-ID: <1624352816-26450-1-git-send-email-wangqing@vivo.com> (raw)
When the CPU suspend, in order to achieve a more power-saving effect,
it is hoped that the CPU sleeps as long as possible, but the timer is an
important reason for the CPU to wake up.
In some cases, when the CPU suspend, the timer doesn’t have to work either,
such as watchdog hrtimer. The maximum suspend time of the CPU is 4s if enable
lockup detector, which is unacceptable on some products, and in fact, watchdog
timer can suspend when the cpu suspend.
This is a patch for comments, I'm not sure if there any ill-considerations.
If this feature is really needed, I will continue to develop.
Wang Qing (2):
hrtimer: support hrtimer suspend when CPU suspend
watchdog: support watchdog hrtimer suspend when CPU suspend
include/linux/hrtimer.h | 3 +++
kernel/time/hrtimer.c | 4 +++-
kernel/time/tick-sched.c | 7 +++++++
kernel/watchdog.c | 3 ++-
--
2.7.4
next reply other threads:[~2021-06-22 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 9:06 Wang Qing [this message]
2021-06-22 9:06 ` [PATCH RFC 1/2] hrtimer: support hrtimer suspend when CPU suspend Wang Qing
2021-08-10 14:58 ` Thomas Gleixner
2021-06-22 9:06 ` [PATCH RFC 2/2] watchdog: support watchdog " Wang Qing
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=1624352816-26450-1-git-send-email-wangqing@vivo.com \
--to=wangqing@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=santosh@fossix.org \
--cc=tglx@linutronix.de \
/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).