linux-kernel - Re: [PATCH V2] watchdog: optimizing the hrtimer interval for power saving

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121128154242.GS14805@redhat.com>
Date:	Wed, 28 Nov 2012 10:42:42 -0500
From:	Don Zickus <dzickus@...hat.com>
To:	Chuansheng Liu <chuansheng.liu@...el.com>
Cc:	akpm@...ux-foundation.org, mingo@...nel.org, rjw@...k.pl,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] watchdog: optimizing the hrtimer interval for power
 saving

On Wed, Nov 28, 2012 at 07:24:52PM +0800, Chuansheng Liu wrote:
> 
> By default, the watchdog threshold is 10, it means every 4s
> every CPU will receive one hrtimer interrupt, for low power
> device, it will cause 4-5mV power impact when device is deep
> sleep.
> 
> So here want to optimize it as below:
> 4s + 4s + 4s + 4s + 4s
> == >
> 1s + 9s + 9s ...
> Or
> 1s + 1s..+ 9s + 9s ....
> 
> For soft lockup detection, it will have more than 5 chances to
> hit, once one chance is successful, we will start 9s hrtimer
> instead of 1s;
> 
> For hard lockup dection, it will have more than 2 chances to hit,
> As Don said, the min window is 10s just when CPU is always running
> as MAX frequency. In most case, the window is 60s, so we should
> have much more than 2 chances.
> 
> With this patch, in most cases the hrtimer will be 9s instead
> of 4s averagely. It can save the device power indeed.
> 
> Change log:
> Since V1: In V1, Don pointed out, "12 seconds will miss the window
>           repeatedly." So here set the long period < min window 10s.

Hmm.  My only concern is if you are solving this the right way.  The
Chrome folks wanted this threshold to be smaller like 2 seconds, which
would defeat the whole point of this patch.

It seems like a better approach would be to adjust the timer somehow when
you change c-states.  The whole point of the hard and softlockup is to
detect if scheduled code is either deadlock or hogging the cpu for too long.

If the cpu is in a deep sleep, then nothing is running, right?  Which
means nothing can deadlock or hog the cpu.  In those cases you can
probably temporarily disable the lockup detector until the cpu wakes up
from that c-state and starts scheduling code again.

In that case you can really maximize your power savings (and probably get
powerTop to stop telling everyone to disable the nmi_watchdog :-) ).

Ideally in a deep sleep you don't want any soft interrupts running, no?

Just a thought.

Cheers,
Don
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/