From: John <linux.kernel@free.fr>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@timesys.com>,
a.p.zijlstra@chello.nl, mingo@elte.hu, johnstul@us.ibm.com,
akpm@osdl.org
Subject: Re: One-shot high-resolution POSIX timer periodically late
Date: Fri, 09 Feb 2007 16:25:11 +0100 [thread overview]
Message-ID: <45CC9257.8080806@free.fr> (raw)
In-Reply-To: <1170955962.3646.51.camel@chaos>
Thomas Gleixner wrote:
> On Wed, 2007-02-07 at 11:25 +0100, John wrote:
>
>> Are there people that use the -rt patch set in real industrial applications?
>
> Yes. But we use a stabilized version of 2.6.16-rt29.
> http://www.osadl.org/projects/downloads/preempt-rt/linux-2.6.16/
Thanks for the pointer.
I'm confused: patch-2.6.16-rt29-tglx3 is dated 2006-09-07, yet there
have been numerous revisions of the -rt patch set since then. Does that
mean that no serious bugs have been found since September? Do the -rt
patch sets for 2.6.17 - 2.6.20 only bring new features and/or adapt the
-rt infrastructure to the newer kernels?
>> It seems that, if an important bug is found in the -rt part, I will have
>> to either upgrade to the latest kernel, or back port all the -rt changes
>> to the kernel I chose for my application?
>
> Yep.
Ouch :-)
I think I'll try my luck with 2.6.20 (it's been working so far).
By the way, I have a question: when I compile glibc for this system,
should I compile it against the vanilla 2.6.20 includes, or against the
patched 2.6.20-rt includes?
Regards.
next prev parent reply other threads:[~2007-02-09 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.4zD54Ie6Ozt0P4YqQSicS+XzXGw@ifi.uio.no>
[not found] ` <fa.G+/T32f2o1M3+YGLca/O8NaAQyY@ifi.uio.no>
[not found] ` <fa.6Ua8xjNfLKQEZZgDsoJgPMyww4g@ifi.uio.no>
[not found] ` <fa.yQlV+WU0TgrJTVqjopa01tgCnT0@ifi.uio.no>
[not found] ` <fa.ucVrLJ1Lh6FjdBHRglsIUc8/evk@ifi.uio.no>
[not found] ` <fa.Id9oufyELrVbe5Wb8SRakwC0V50@ifi.uio.no>
2007-02-01 10:18 ` One-shot high-resolution POSIX timer periodically late John
2007-02-06 12:37 ` Ingo Molnar
2007-02-07 10:13 ` John
2007-02-05 16:37 ` John
2007-02-06 7:31 ` Peter Zijlstra
2007-02-07 10:25 ` John
2007-02-08 17:32 ` Thomas Gleixner
2007-02-09 15:25 ` John [this message]
2007-02-09 16:21 ` Benedikt Spranger
2007-02-09 16:43 ` Thomas Gleixner
[not found] <fa.mtUvfgenNQkCc8835prYbwyiPQs@ifi.uio.no>
[not found] ` <fa.lwkMc548uRMcUjd9KZ2pC1DMKT4@ifi.uio.no>
[not found] ` <fa.dTtI0ctv1nu+tCWiK6jGPnrX69k@ifi.uio.no>
[not found] ` <fa.CMU3scpnLxfHVWRFPcmfRl2CjhA@ifi.uio.no>
2007-01-30 17:38 ` John
2007-01-30 20:25 ` Ingo Molnar
[not found] <fa.NwnlFyMPfa3XG6my3HKGWnCW3x4@ifi.uio.no>
[not found] ` <fa.Ji4GnAbBF2FR5JbSxvxn2haJZIk@ifi.uio.no>
2007-01-25 9:59 ` John
2007-01-25 22:19 ` john stultz
[not found] ` <fa.8TBiwbgs8B881k+3X+IlFjhqpLI@ifi.uio.no>
2007-01-25 12:03 ` John
[not found] <45B729AF.4030701@privacy.net>
2007-01-24 19:02 ` john stultz
2007-01-24 20:09 ` Ingo Molnar
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=45CC9257.8080806@free.fr \
--to=linux.kernel@free.fr \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@timesys.com \
/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.