From: Wim Van Sebroeck <wim@iguana.be>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Simon Braunschmidt <sb@emlix.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: Handling multiple watchdogs
Date: Wed, 23 Feb 2011 08:55:34 +0100 [thread overview]
Message-ID: <20110223075534.GN3790@infomag.iguana.be> (raw)
In-Reply-To: <20110202111516.0154bb4a@lxorguk.ukuu.org.uk>
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.
prev parent reply other threads:[~2011-02-23 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 15:09 Simon Braunschmidt
2009-07-22 16:19 ` Alan Cox
2009-07-22 18:52 ` Wim Van Sebroeck
2011-02-02 11:15 ` Alan Cox
2011-02-23 7:55 ` Wim Van Sebroeck [this message]
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=20110223075534.GN3790@infomag.iguana.be \
--to=wim@iguana.be \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=sb@emlix.com \
/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
all inboxes | Powered by JetHome®