From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: PREEMPT_RT support
Date: Mon, 06 Dec 2010 19:35:08 -0800 [thread overview]
Message-ID: <4CFDAB6C.2080600@linux.intel.com> (raw)
In-Reply-To: <4CFD871A.10904@windriver.com>
On 12/06/2010 05:00 PM, Bruce Ashfield wrote:
> On 10-12-06 6:06 PM, Darren Hart wrote:
>> I'm looking at how to best support PREEMPT_RT. We have a few things in
>> the works which prevent the ideal scenario (which is just a new recipe
>> using the preempt_rt branch in linux-yocto).
>>
>> 2.6.34 never had an -rt patch. The WR folks created one that builds and
>> is undergoing review from tglx - but that doesn't appear to be near the
>> top of his stack. 2.6.37 is still pending an -rt patch, also blocked on
>> -tglx.
>
> We'll be doing one at WR eventually, so it will exist in
> one form or another for version > 2.6.34.
My wording above wasn't quite right. tglx will be releasing a 2.6.37 -rt
tree, that is committed. We're just waiting for it to emerge. There are
a handful of reworks that will begin with 2.6.37 and may delay things
some, but it will emerge.
>
>>
>> I'm thinking of creating a meta-rt layer which would provide a latest
>> -rt kernel and the rt-tests suite along with a non-graphical image
>> definition that facilitates latency detection and rt performance
>> measurement. poky-image-rt-test or something along those lines.
>>
>> Any objection to this approach? As we will eventually move these recipes
>> into the core poky recipes, I'd suggest we put this in an
>> "experimental/meta_rt" git repository.
>
> I'm worrying about this muddying the water with respect to the
> -rt branches in the linux-yocto repositories. In particular if
> we go *backward* from the 2.6.34 variant that we already have
> (remember, that -rt kernel has been heavily abused for 9
> months now and is just as stable (probably more so for
> non-x86) as anything else you'll find).
>
> Why can't we continue to consolidate these into fewer kernels
> and recipes ? We can't share fixes and BSPs easily if everything
> is kept separate. We can obviously pair the tests/utilities along
> with the linux-yocto -rt branches, so I'd prefer that approach
> and continue to work on improving the base that we already
> have.
Hrm. Perhaps my perception of the 2.6.34 kernel is flawed. I wasn't
aware that this particular version of the patch had seen so much
runtime. If that is the case, instead of an rt-layer, I'll just prepare
an rt kernel recipe (as we discussed) using the linux-yocto kernel and
add rt-tests. Both to the core poky meta dir.
I think it would still make sense to have a linux-rt_tip.bb, which
builds from linux-2.6-tip.git/rt/head as a sort of developers kernel.
Perhaps this would work well with the other dev recipes you have simmering?
--
Darren Hart
Yocto Linux Kernel
next prev parent reply other threads:[~2010-12-07 3:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 23:06 PREEMPT_RT support Darren Hart
2010-12-07 1:00 ` Bruce Ashfield
2010-12-07 1:04 ` Bruce Ashfield
2010-12-07 3:35 ` Darren Hart [this message]
2010-12-07 15:35 ` Bruce Ashfield
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=4CFDAB6C.2080600@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox