linux-kernel - Re: [PATCH 1/10 v2] Generic Watchdog Timer Driver

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]

Date:	Wed, 22 Jun 2011 22:25:46 +0200
From:	Wim Van Sebroeck <wim@...ana.be>
To:	Chris Friesen <chris.friesen@...band.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux Watchdog Mailing List <linux-watchdog@...r.kernel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 1/10 v2] Generic Watchdog Timer Driver

Hi Chris,

>> watchdog: WatchDog Timer Driver Core - Part 1
>>
>> The WatchDog Timer Driver Core is a framework
>> that contains the common code for all watchdog-driver's.
>> It also introduces a watchdog device structure and the
>> operations that go with it.
>>
>> This is the introduction of this framework. This part
>> supports the minimal watchdog userspace API (or with
>> other words: the functionality to use /dev/watchdog's
>> open, release and write functionality as defined in
>> the simplest watchdog API). Extra functionality will
>> follow in the next set of patches.
>
>
> Have you thought about callback support for systems that support a  
> two-stage watchdog?  That way we could do something useful (preserve  
> system memory using kdump, for instance) rather than just getting  
> whacked by the hardware.

No, goal was to first have an API that reduces the existing functionality
that we copy over in each driver.
But it's indeed a feauture where we should look at in the future.
Question will be: how will we implement it.

Kind regards,
Wim.

--
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/