All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Meduna <stano@meduna.org>
To: linux-rt-users@vger.kernel.org
Subject: Re: RT_PREEMPT autodetection from user program
Date: Sun, 20 Jan 2013 10:49:28 +0100	[thread overview]
Message-ID: <50FBBDA8.5060605@meduna.org> (raw)
In-Reply-To: <97041258-E312-4163-96B2-9077EED68E0B@mah.priv.at>

On 20.01.2013 01:13, John Morris wrote:

> LCNC drives machines that weigh many tons and spins
> spindles at 24k RPM, so this is important!
...
> We haven't found /proc/config.gz in any vendor-provided
> PREEMPT_RT kernels, so that is not an option either.

On 20.01.2013 01:49, Michael Haberler wrote:

> A false positive on a vanilla kernel could be a safety hazard.

If we are speaking safety here I'd say that you have to support
specific version of kernel on specific hardware that _you_ have
quality assured. Anything else is a recipe for problems.

I've seen OSADL Linux deadlock, RT PREEMPT leaking memory,
RT PREEMPT on but without high-res timers, IDE driver
monopolizing processor so that the RT throttler was activated,
priority inversion issues between kernel and application
threads, interrupt latencies due to interrupt routing
on the specific hardware etc.

There is no way you can guarantee anything if you are using
vendor-provided kernel on a hardware you have never seen.
With your kernel, a list of supported hardware, with initscripts
that are checking if the environment matches and with the help
from this list (thank you guys, the level of support here
is excellent!) you will sleep a lot better.

Just my two cents

Regards
-- 
                                        Stano


  parent reply	other threads:[~2013-01-20 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20  0:49 RT_PREEMPT autodetection from user program Michael Haberler
2013-01-20  1:56 ` Sven-Thorsten Dietrich
2013-01-20  9:49 ` Stanislav Meduna [this message]
2013-01-20 12:43   ` Michael Mueller
2013-01-21 15:37 ` Clark Williams

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=50FBBDA8.5060605@meduna.org \
    --to=stano@meduna.org \
    --cc=linux-rt-users@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.