All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "fixed-term.Oleksij.Rempel"
	<fixed-term.Oleksij.Rempel@de.bosch.com>,
	linux-watchdog@vger.kernel.org,
	"Dirk.Behme" <Dirk.Behme@de.bosch.com>
Subject: Re: watchdoug group ping
Date: Thu, 21 Apr 2016 07:52:20 -0700	[thread overview]
Message-ID: <5718E924.2030103@roeck-us.net> (raw)
In-Reply-To: <57172B7C.4060407@de.bosch.com>

On 04/20/2016 12:10 AM, fixed-term.Oleksij.Rempel wrote:
> Hallo all,
>
> my target is to provide pretimout support for devices which do not have
> this functionality.
>
> Pre-requirement is this patchset (i contacted the author to rebase it
> against latest watchdog core branch):
> https://www.mail-archive.com/linux-watchdog@vger.kernel.org/msg02394.html
>
> The idea is to use different watchdogs/timers or what ever as one group
> - one virtual device.
> One driver will be responsible for reseting the system, other for
> generating an interrupt on pre-timout.
> It can be also useful for systems which require redundant watchdogs -
> two or more watchdog pinged over one /dev/watchdog
>
> I assume i would need to create a master virtual watchdog driver to
> bypass/broadcast all pings to child devices.
>
> Do you have some ideas or suggestions?
>
Seems to add a lot of complexity. It might be much simpler to add support
for a 'soft' pretimeout in such situations, ie a timer which fires at the
correct interval and results in a reset. It might even be possible to use
the new internal heartbeat function for this purpose.

Guenter


  reply	other threads:[~2016-04-21 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  7:10 watchdoug group ping fixed-term.Oleksij.Rempel
2016-04-21 14:52 ` Guenter Roeck [this message]
2016-04-21 20:25   ` Oleksij Rempel

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=5718E924.2030103@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Dirk.Behme@de.bosch.com \
    --cc=fixed-term.Oleksij.Rempel@de.bosch.com \
    --cc=linux-watchdog@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.