All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: PREEMPT_RT support
Date: Mon, 06 Dec 2010 20:00:10 -0500	[thread overview]
Message-ID: <4CFD871A.10904@windriver.com> (raw)
In-Reply-To: <4CFD6C73.20006@linux.intel.com>

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.

>
> 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.

Cheers,

Bruce

>
> Thoughts?
>



  reply	other threads:[~2010-12-07  1:00 UTC|newest]

Thread overview: 8+ 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 [this message]
2010-12-07  1:04   ` Bruce Ashfield
2010-12-07  3:35   ` Darren Hart
2010-12-07 15:35     ` Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2024-09-30  8:19 Jean-Michel Hautbois
2024-09-30  8:38 ` John Paul Adrian Glaubitz
2024-10-01  2:24   ` Michael Schmitz

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=4CFD871A.10904@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.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 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.