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 22:05:57 +0100	[thread overview]
Message-ID: <494D5E35.2010208@domain.hid> (raw)
In-Reply-To: <494D5CFE.8020406@domain.hid>

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

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> 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.
> 
> I disagree: the current version compiles in all configurations tested
> until now, and happened to work when enabled at some point in the past.
> I find it annoying, to say the least, when I want to test something on
> trunk, that some previous unrelated commit breaks a configuration
> because it was not tested. So, please test your patch. The
> configurations to test are not so numerous: disabled, enabled built-in
> with an overrun check, enabled in module with an overrun check, repeat
> for x86_64. That makes 6 configurations, not that much.

The trivial ones have been tested, of course. But keep in mind that
there are more variables (CPU types , kernel versions, interfering
config settings, etc.) that create much more that 6 variants to be built
and run.

Jan


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

  reply	other threads:[~2008-12-20 21:05 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 3/3] Rework x86 NMI watchdog pass-through 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 1/3] Update NMI watchdog for latest Intel CPUs 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
2008-12-20 21:00     ` Gilles Chanteperdrix
2008-12-20 21:05       ` Jan Kiszka [this message]
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=494D5E35.2010208@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.