Re: Handling multiple watchdogs

[Wim Van Sebroeck]

Hi Alan,

> > 1) make sure that we have the new watchdog core infrastructure going in for 2.6.32.
> > This new core integrates the common code that we use over and over again. I once
> > wrote code for it and then Alan had different ideas and thoughts and wrote his updated
> > code. I reviewed that and I am changing some small bits so that we will have the new
> 
> What is the status of this ? I was thinking it had been a while but it
> seems to be 18 months ago..

I did that dev_* fix as we agreed on sunday.
I will sent out the code (for additional comments) out tonight to linux-kernel and linux-watchdog mailing lists.
Aiming to get it in for 2.6.39.

Code can allready be looked at, at:
http://git.kernel.org/?p=linux/kernel/git/wim/linux-2.6-watchdog-next.git;a=shortlog;h=refs/heads/generic-watchdog

Open issues: get min adn max timeout in so that the generic code can check the boundarys.
Need to think about MAGIC_CLOSE_FEATURE. There seem to be people that are surprised that if you do a cat /dev/watchdog that the system reboots. Whiwh is normal: it's an open with a close without the magic character. One solution I see is to add a module_param that can disable magic_close_feature. Default will be on though).

And after that we can consider the read function that you proposed.

And then we need to go for the sysfs interface so that we can support multiple watchdogs via sysfs.

Kind regards,
Wim.

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