All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai@xenomai.org
Subject: Re: [Xenomai-core] [RFC] Getting rid of the NMI latency watchdog
Date: Wed, 22 Jun 2011 22:47:45 +0200	[thread overview]
Message-ID: <1308775665.2159.98.camel@domain.hid> (raw)
In-Reply-To: <4E022367.7020200@domain.hid>

On Wed, 2011-06-22 at 19:16 +0200, Gilles Chanteperdrix wrote:
> On 05/19/2011 10:29 PM, Philippe Gerum wrote:
> > On Thu, 2011-05-19 at 20:36 +0200, Jan Kiszka wrote:
> >> On 2011-05-19 20:15, Gilles Chanteperdrix wrote:
> >>> On 05/19/2011 03:58 PM, Philippe Gerum wrote:
> >>>> For this reason, I'm considering issuing a patch for a complete removal
> >>>> of the NMI latency watchdog code in Xenomai 2.6.x, disabling the feature
> >>>> for 2.6.38 kernels and above in 2.5.x.
> >>>>
> >>>> Comments welcome.
> >>>
> >>> I am in the same case as you: I no longer use Xeno's NMI watchdog, so I
> >>> agree to get rid of it.
> >>
> >> Yeah. The last time we wanted to use it get more information about a
> >> hard hang, the CPU we used was not supported.
> >>
> >> Philippe, did you test the Linux watchdog already, if it generate proper
> >> results on artificial Xenomai lockups on a single core?
> > 
> > This works provided we tell the pipeline to enter printk-sync mode when
> > the watchdog kicks. So I'd say that we could probably do a better job in
> > making the pipeline core smarter wrt NMI watchdog context handling than
> > asking Xenomai to dup the mainline code for having its own NMI handling.
> 
> If nobody disagrees, I am removing this code from -head. Now.
> 

Ack.

-- 
Philippe.




      reply	other threads:[~2011-06-22 20:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 13:58 [Xenomai-core] [RFC] Getting rid of the NMI latency watchdog Philippe Gerum
2011-05-19 18:15 ` Gilles Chanteperdrix
2011-05-19 18:36   ` Jan Kiszka
2011-05-19 20:29     ` Philippe Gerum
2011-06-22 17:16       ` Gilles Chanteperdrix
2011-06-22 20:47         ` Philippe Gerum [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=1308775665.2159.98.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --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.