linux-kernel - Re:Re: [PATCH V9 1/2] watchdog: mtk: support pre-timeout when the bark irq is available

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] [day] [month] [year] [list]

Date:   Mon, 17 May 2021 16:37:21 +0800 (GMT+08:00)
From:   王擎 <wangqing@...o.com>
To:     Wim Van Sebroeck <wim@...ux-watchdog.org>
Cc:     linux-arm-kernel@...ts.infradead.org,
        linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Guenter Roeck <linux@...ck-us.net>
Subject: Re:Re: [PATCH V9 1/2] watchdog: mtk: support pre-timeout when the bark irq is available


>On 5/5/21 6:51 PM, 王擎 wrote:
>> 
>>> On 4/24/21 6:52 PM, Wang Qing wrote:
>>>> Use the bark interrupt as the pretimeout notifier if available.
>>>>
>>>> When the watchdog timer expires in dual mode, an interrupt will be
>>>> triggered first, then the timing restarts. The reset signal will be
>>>> initiated when the timer expires again.
>>>>
>>>> The pretimeout notification shall occur at timeout-sec/2.
>>>>
>>>> V2:
>>>> - panic() by default if WATCHDOG_PRETIMEOUT_GOV is not enabled.
>>>>
>>>> V3:
>>>> - Modify the pretimeout behavior, manually reset after the pretimeout
>>>> - is processed and wait until timeout.
>>>>
>>>> V4:
>>>> - Remove pretimeout related processing. 
>>>> - Add dual mode control separately.
>>>>
>>>> V5:
>>>> - Fix some formatting and printing problems.
>>>>
>>>> V6:
>>>> - Realize pretimeout processing through dualmode.
>>>>
>>>> V7:
>>>> - Add set_pretimeout().
>>>>
>>>> V8/V9:
>>>> - Fix some formatting problems.
>>>>
>>>> Signed-off-by: Wang Qing <wangqing@...o.com>
>>>
>>> Reviewed-by: Guenter Roeck <linux@...ck-us.net>
>>>
>>> Note that the version history should be after "---".
>>>
>>> Guenter
>>>
>> 
>> Thanks, Guenter.
>> And what do I need to do if I want merge into the next-tree?
>> 
>Wim should take care of that.
>
>Guenter
>
Wim, can you help to pick it up to the next-tree?

Thanks,
Qing