All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [PATCH  0/3] NMI watchdog fixes / enhancements
Date: Sat, 20 Dec 2008 21:48:00 +0100	[thread overview]
Message-ID: <494D5A00.6070809@domain.hid> (raw)
In-Reply-To: <494D1ED5.2090300@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> This is basically a repost of the NNI watchdog series I sent out a few
>> weeks ago. I just rebased things over latest trunk and fixed some
>> warnings.
>>
>> All patches are also available at
>> git://git.kiszka.org/xenomai.git nmi-wd-queue
> 
> That is a lot of stuff to review. I am afraid it is impossible to review
> everything, so the only thing we can rely on is testing, hence the next
> question: have these patches been tested in every configuration
> (enabled, disabled, built-in, module, voluntary overrun)?

In most configurations, but definitely not in all (they are too many).

This is a debugging tool, so first of all the disabled case must not
cause harm, and I'm quite sure I haven't changed anything regarding
this. Moreover, the enabled case was not working for many recent
platforms anymore as we were lacking P6 support. So there shouldn't be
much to loose.

> 
> As for the 32nd bit issue, I am afraid it can not explain the spurious
> shots observed on some platfomrs (note that I implemented the early shot
> thing a bit in the dark: I never observed the spurious shots myself),
> that is because the nmi timer is programmed for durations between 100us
> and 10ms, which should be far from using the 32nd bit.

Yes, the signedness issue that is fixed in patch 1 has likely nothing to
do with the spurious invocations. But wherever they may still come from,
patch 3 ensures that they are now properly ignored (ie. forwarded to the
next handling instance).

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2008-12-20 20:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  8:44 [Xenomai-core] [PATCH 0/3] NMI watchdog fixes / enhancements Jan Kiszka
2008-12-19  8:44 ` [Xenomai-core] [PATCH 1/3] Update NMI watchdog for latest Intel CPUs Jan Kiszka
2008-12-19  8:44 ` [Xenomai-core] [PATCH 2/3] NMI watchdog support for x86-64 Jan Kiszka
2008-12-19  8:44 ` [Xenomai-core] [PATCH 3/3] Rework x86 NMI watchdog pass-through Jan Kiszka
2008-12-20 16:35 ` [Xenomai-core] [PATCH 0/3] NMI watchdog fixes / enhancements Gilles Chanteperdrix
2008-12-20 20:48   ` Jan Kiszka [this message]
2008-12-20 21:00     ` Gilles Chanteperdrix
2008-12-20 21:05       ` Jan Kiszka
2008-12-20 21:37         ` Jan Kiszka

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=494D5A00.6070809@domain.hid \
    --to=jan.kiszka@domain.hid \
    --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.