[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45C9A8FE.3090705@free.fr>
Date: Wed, 07 Feb 2007 11:25:02 +0100
From: John <linux.kernel@...e.fr>
To: linux-kernel@...r.kernel.org
CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>, tglx@...esys.com,
mingo@...e.hu, johnstul@...ibm.com, akpm@...l.org,
linux.kernel@...e.fr
Subject: Re: One-shot high-resolution POSIX timer periodically late
Peter Zijlstra wrote:
> John wrote:
>
>> Ingo Molnar wrote:
>>
>>> John wrote:
>>>
>>>> John Stultz wrote:
>>>>
>>>>> Also do check the -rt tree as Ingo suggested. I mis-read your earlier
>>>>> email and thought you were running it.
>>>>
>>>> I've been pulling my hair over a related issue for the past two days.
>>>>
>>>> (I think I may be tickling a -hrt bug...)
>>>>
>>>> I'm working with 2.6.18.6 + patch-2.6.18-rt7
>>>
>>> 2.6.18-rt7 is pretty old, do you see the problem in 2.6.20-rc6-rt5 too?
>>
>> Ingo, Thomas,
>>
>> As far as I can tell, the -rt patch set is only updated for the latest
>> kernel version available. Is that correct?
>>
>> http://people.redhat.com/mingo/realtime-preempt/older/?M=D
>>
>> In other words, once 2.6.20 is released, and work starts on 2.6.21, if a
>> bug is discovered in -rt, the fix will not be back-ported to the
>> 2.6.20.x (and 2.6.19.x, and 2.6.18.x, etc) patch set?
>
> Correct, there is only 1 live branch.
Are there people that use the -rt patch set in real industrial applications?
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?
Regards,
John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists