All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Insop Song <insop.song@gmail.com>
Cc: yocto@yoctoproject.org, Darren Hart <dvhart@linux.intel.com>
Subject: Re: A question on adding a new program to a new meta layer
Date: Sun, 10 Mar 2013 23:28:56 -0400	[thread overview]
Message-ID: <513D4F78.9010307@windriver.com> (raw)
In-Reply-To: <CACzyEJ9MHVD8GyVEwXkdndmQy7DQ_Tt-M0n6-0dWG7LOHgVR5w@mail.gmail.com>

On 13-03-09 5:32 AM, Insop Song wrote:
> On Fri, Mar 8, 2013 at 3:35 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com>  wrote:
>> On 13-03-08 12:01 PM, Darren Hart wrote:
>>>
>>>
>>>
>>> On 03/04/2013 08:04 PM, Insop Song wrote:
>>>>
>>>> Hi,
>>>>
>>>> I am preparing a new meta layer for testing and promoting a
>>>> sched_deadline scheduler, called "meta-dl". I am planning to add
>>>> scheduler testing tools and different kernel versions as well.
>>>> - http://insop.github.com/meta-dl/
>>>
>>>
>>> Note that qemux86 doesn't support the EMGD graphics driver. You mention
>>> this and its license in the README, but it isn't necessary. If you are
>>> pulling that in, there is a problem with your recipes.
>>
>>
>> wow. mailing list delays are making this conversation *extremely*
>> painful and disjointed.
>>
>>
> Darren,
> Those that you've mentioned were from yocto kernel lab examples.
> I went over and cleaned them up. https://github.com/insop/meta-dl
>
> However, at this point, I am more looking at meta-realtime that uses
> yocto-linux-3.8 instead as Bruce's suggestion.
> https://github.com/insop/meta-realtime


Expect that the yocto project hosted meta-realtime will appear in a
week or so. I'm doing the legwork at the moment, but with some travel
in the upcoming week, the initial push will be delayed by a few days.

Cheers,

Bruce

>
>
>>>
>>> So you are using the sched_deadline patches, but not PREEMPT_RT, is that
>>> right? I had always assumed sched_deadline ran on top of PREEMPT_RT (but
>>> I haven't every tried building it myself).
>>
>>
>> sched_deadline applies to mainline, right on top of CFS as a scheduler
>> class. So in fact, I wouldn't suggest it with preempt-rt at all at the
>> moment.
>>
>>
>
> Right, previously, Juri maintained sched_deadline on top of
> preempt-rt, but not any more.
>
>>>
>>> What you have here is a good experimental layer. Looking forward, please
>>> consider:
>>>
>>> o Incorporating sched_deadline as a kernel feature into the
>>> linux-yocto_3.8 kernel. We can easily add recipes to build a
>>> linux-yocto-deadline kernel and you will get all the benefits of the
>>> yocto tooling, testing, bugfixing, and free forward porting.
>>
>>
>> Already done. I've had it in linux-yocto-3.8 since I first introduced
>> it. We just need the supporting userspace to easily change the
>> scheduler class for a process.
>>
>>
>
> Yup, two apps that can test sched_deadline is at meta-realtime now.
> I will prepare some script to make it easier as well.
>
>>>
>>> o Incorporating your tests into (poky|oe-core)/meta/recipes-rt
>>
>>
>> Or if they aren't fully 'core', our new meta-realtime that I'd like
>> to have created shortly.
>>
>
> I will be playing with meta-realtime at github until you create one.
> Please let me know if you have any other requested program on this layer.
>
> Regards,
>
> Insop



  reply	other threads:[~2013-03-11  3:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACzyEJ_3BRjn4s7ADey9uuQpGhgWKeuuyxGVL09HuLAzJ3LqTQ@mail.gmail.com>
2013-03-05  6:54 ` A question on adding a new program to a new meta layer Insop Song
2013-03-07  4:00   ` Bruce Ashfield
2013-03-07  4:24     ` Juri Lelli
2013-03-07 13:53       ` Bruce Ashfield
2013-03-07 21:49         ` Insop Song
2013-03-08  1:46           ` Bruce Ashfield
2013-03-08  4:12             ` Insop Song
2013-03-07  5:05     ` Insop Song
2013-03-07  8:26       ` Insop Song
2013-03-07 14:05         ` Bruce Ashfield
2013-03-07 22:02           ` Insop Song
2013-03-08  1:47             ` Bruce Ashfield
2013-03-08 11:10               ` Insop Song
2013-03-07 14:04       ` Bruce Ashfield
2013-03-08 13:27         ` Insop Song
2013-03-08 16:32           ` Bruce Ashfield
2013-03-08 17:03         ` Darren Hart
2013-03-08 17:36           ` Bruce Ashfield
2013-03-07 14:08       ` Bruce Ashfield
2013-03-07 21:43         ` Insop Song
2013-03-08  1:45           ` Bruce Ashfield
2013-03-08  4:02           ` Juri Lelli
2013-03-05  9:19 ` Insop Song
2013-03-08 17:01 ` Darren Hart
2013-03-08 23:35   ` Bruce Ashfield
2013-03-09 10:32     ` Insop Song
2013-03-11  3:28       ` Bruce Ashfield [this message]
2013-03-11  3:32         ` Insop Song
2013-03-11 14:34           ` Bruce Ashfield
2013-03-11 16:07             ` Insop Song
2013-03-11 17:03               ` Bruce Ashfield
2013-03-11 17:20                 ` Insop Song

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=513D4F78.9010307@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=insop.song@gmail.com \
    --cc=yocto@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.