LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: John <linux.kernel@free.fr>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
tglx@timesys.com, mingo@elte.hu, johnstul@us.ibm.com,
akpm@osdl.org, linux.kernel@free.fr
Subject: Re: One-shot high-resolution POSIX timer periodically late
Date: Wed, 07 Feb 2007 11:25:02 +0100 [thread overview]
Message-ID: <45C9A8FE.3090705@free.fr> (raw)
In-Reply-To: <1170747081.4672.11.camel@twins>
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
next prev parent reply other threads:[~2007-02-07 10: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 ` 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 [this message]
2007-02-08 17:32 ` Thomas Gleixner
2007-02-09 15:25 ` John
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=45C9A8FE.3090705@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 \
--subject='Re: One-shot high-resolution POSIX timer periodically late' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).