From: John Sigler <linux.kernel@free.fr>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, tglx@linutronix.de
Subject: Re: Old -rt patches
Date: Tue, 07 Aug 2007 10:27:09 +0200 [thread overview]
Message-ID: <46B82CDD.7020503@free.fr> (raw)
In-Reply-To: <1186466508.22044.8.camel@imap.mvista.com>
Daniel Walker wrote:
> John Sigler wrote:
>
>> Would anyone care to comment?
>
> I'm not sure if this is the answer that you're looking for, but yes you
> certainly will find fixed bug is older version of the tree.
I am not a kernel hacker, therefore I can only imagine how complex it is
to bring real-time to Linux. For some reason, I had come to believe that
the case of a single CPU without dynticks had been "solved" in the more
recent kernels (say 2.6.20), and that development had moved on, and was
now active in more "complex" areas like SMP/multi-core, dynticks, etc.
>> Perhaps I could also test a different strategy, such as xenomai?
>> http://www.xenomai.org/
>
> If it's a kernel bug it's not going to matter if you use a xenomai skin
> or not.. If you use some other real time layer that might fix it ..
*If* it is a bug in the -rt patch, then Adeos/Xenomai coupled with a
vanilla Linux kernel should not be affected by the same bug. Unless my
logic is broken somewhere.
> you really need to test your app on a current version of the kernel ..
> We as developers generally don't support out dated trees..
This is the part I don't understand. I work for a tiny company with
limited resources. It's infeasible for me to track every new kernel
release and upgrade every time. I need to pick a kernel version that has
the functionality we need, test it thoroughly with my app, and then
never touch that kernel again.
Unless I am mistaken, some people (like Thomas) have been deploying
systems based on PREEMPT_RT (or just -hrt) in indutrial settings for a
long time. (As far back as 2.6.15?) Obviously many bugs have been fixed
since then, which means that these versions contained many bugs.
How does one react when an important bug in found in a system that is
already in the field? Do they provide a way to upgrade the kernel (like
consumer-grade network routers)? Do they replace the complete system?
Regards.
next prev parent reply other threads:[~2007-08-07 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 16:41 Old -rt patches John Sigler
2007-08-06 8:55 ` John Sigler
2007-08-06 14:41 ` Paul E. McKenney
2007-08-07 8:52 ` John Sigler
2007-08-07 6:01 ` Daniel Walker
2007-08-07 8:27 ` John Sigler [this message]
2007-08-07 15:10 ` Daniel Walker
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=46B82CDD.7020503@free.fr \
--to=linux.kernel@free.fr \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox