From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Insop Song <insop.song@gmail.com>
Cc: Darren Hart <dvhart@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: A question on adding a new program to a new meta layer
Date: Fri, 8 Mar 2013 11:32:39 -0500 [thread overview]
Message-ID: <513A12A7.7040401@windriver.com> (raw)
In-Reply-To: <CACzyEJ9nXL0E_HggNbYcv5gO7zzXFZj1pLBwkH248DVB3BWRyg@mail.gmail.com>
On 13-03-08 08:27 AM, Insop Song wrote:
> On Thu, Mar 7, 2013 at 6:04 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 13-03-07 12:05 AM, Insop Song wrote:
>>>
>>> Bruce,
>>>
>>> That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
>>> (https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
>>
>>
>> I have another suggestion to offer here, one I've been wanting to
>> do for a bit.
>>
>> I've added Darren Hart to the thread, since I'd like to hear from
>> him on this as well.
>>
>> I have a use for the scheduling tools and benchmark cases for some
>> virtualization usecases (meta-virtualization on git.yoctoproject.org).
>>
>> We already have "recipes-rt" in oe-core, and the preempt-rt kernel
>> available from linux-yocto, and as we've been discussing I've added
>> support for EDF/sched_dealine in linux-yocto-3.8.
>>
>> I'm not a fan of having to many layers, but rather than putting these
>> efforts in github layers, hiding them in meta-virtualiation and they
>> aren't yet "core" enough to go in oe-core .. I'd rather see them
>> conslidated in a "meta-realtime" (or whatever name we decide on)
>> layer on git.yoctoproject.org.
>>
>
> meta-realtime sounds good to me, and this can include schedulers
> real-time application and testing suits.
>
>> There are also ideas around interrupt management, AMP, and alternative
>> system partitioning that I'd like to drive into such a layer.
>>
>
> Good idea to add these continuously to the "meta-realtime"
>
>
>> A quick scan of the layer index, doesn't show anything that matches
>> this description. So I'm suggesting that we create a new layer
>> to consolidate these approaches, and a layer that can be consumed by
>> some of the other layers that are currently in progress.
>>
>> Comments ? In particular, point out a layer that already does this that
>> I've missed.
>>
>>
>
> I've took out machine related from my previous meta-dl-qemux86 and put
> together meta-realtime as a starting point. It has two sched_deadline
> testing program.
> It's on github for now for your reference, but I am willing to move or
> merge to git.yocto.
>
> https://github.com/insop/meta-realtime
Thanks. I'll have a look, I have my own local meta-realtime as well,
so I can consolidate the two and see about getting them hosted on
git.yoctoproject.org.
Cheers,
Bruce
>
> Thank you,
>
> Insop
>
next prev parent reply other threads:[~2013-03-08 16:32 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 [this message]
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
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=513A12A7.7040401@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.