From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Make watchdog-timer configurable
Date: Wed, 05 Sep 2007 17:05:32 +0200 [thread overview]
Message-ID: <1189004732.28092.298.camel@domain.hid> (raw)
In-Reply-To: <18142.49532.752950.449999@domain.hid>
On Wed, 2007-09-05 at 16:47 +0200, Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > On Tue, 2007-09-04 at 15:12 +0200, Johan Borkhuis wrote:
> > > I made the following change to Xenomai (version 2.3.2, but it could also
> > > be applied to 2.4 as the watchdog code has not been changed).
> > >
> > > The watchdog timeout is fixed at 4 seconds. For us this is a problem as
> > > there are some processes that take more time than this.
> > >
> > > I made the following change to allow this to be changed through the
> > > Linux kernel configuration. The value is configurable between 1 and 60
> > > seconds.
> > >
> > > Below is a patchfile that implements this change. Please let me know if
> > > you have comments on this, or if there are problems with this change.
> > >
> >
> > Looks good. Will merge, thanks.
>
> I have nothing against the patch.
>
> That said, if you have a real-time activity that does not let Linux run
> for 4 seconds, you are risking some troubles when the real-time activity
> gives back the control to Linux, such as random lockups for example.
>
You could also use this feature to lower the deadline below 4 secs,
which is already pretty high.
--
Philippe.
next prev parent reply other threads:[~2007-09-05 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 13:12 [Xenomai-core] Make watchdog-timer configurable Johan Borkhuis
2007-09-04 13:54 ` Philippe Gerum
2007-09-05 14:47 ` Gilles Chanteperdrix
2007-09-05 15:05 ` Philippe Gerum [this message]
2007-09-07 7:40 ` Philippe Gerum
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=1189004732.28092.298.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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.