Hi,
On 03/06/2013 08:00 PM, Bruce Ashfield wrote:
On 13-03-05 1:54 AM, 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/
FYI: I've already merged and staged sched_dl in linux-yocto_3.8:
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.8/log/?h=standard/edf
I'll be supporting it there as well, so it makes sense to coordinate
our efforts around kernels, configurations and benchmarks.
Juri and I talked about this @ ELC a few weeks ago (I've added
him to the cc as well), and rather than hiding sched_deadline
kernel support in a custom kernel layer, I'd like to try and get
more eyes on it via linux-yocto .. so if we can all coordinate our
efforts here, that would be much better.
Thanks a lot for your support! I'm already in contact with Insop, it
would be great to coordinate among ourselves.
As I already told to Insop, I don't have any automated test for the
patchset, but I usually run different scenarios using basically this
two tools (and giving a look at simple cases through kernelshark):
1- schedtool-dl: https://github.com/jlelli/schedtool-dl
the idea here is to let a 'yes' run through SCHED_DEADLINE and
check through kernelshark that the bandwidth enforcement
mechanism works.
2- rt-app: https://github.com/gbagnoli/rt-app
with this I usually let some tasksets run for several hours on
a 48-cores machine we have in our lab, I can provide the tasksets
(json files) and the script to run them.
Please let me know how I can help further.
Best Regards,
- Juri
With the help of hands-on kernel lab (thank you Tom and Darren), I am
able to make kernel with sched_deadline enabled.
Now, I am having some trouble of adding testing tools to this meta-dl,
and hope I can get some help from you.
- problem: adding a new software into my meta-dl layer
- symtom and questions?
1. bitbake core-image-minimal (normal image build) won't include the
additional program that I listed in .bb file below
2. If I do "bitbake schedtool-dl -c install" it builds and install,
but at "i586" location instead of my machine staging rootfs
(dl-qemux86)
- Here is my .bb file that pulls an additional program.
https://github.com/insop/meta-dl/blob/sched-dl-V7/recipes-tools/schedtool-dl/schedtool-dl.bb
===
DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
HOMEPAGE = "https://github.com/insop/schedtool-dl";
SECTION = "base"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
PR = "r1"
SRC_URI = "git://github.com/insop/schedtool-dl.git;protocol=git"
SRCREV = "${AUTOREV}"
S = "${WORKDIR}/git"
do_compile() {
oe_runmake
}
do_install() {
oe_runmake install DESTDIR=${D}
}
PARALLEL_MAKE = ""
BBCLASSEXTEND = "native"
COMPATIBLE_MACHINE_dl-qemux86 = "dl-qemux86"
====
- I've updated my conf/layer.conf file to include above file
https://github.com/insop/meta-dl/blob/sched-dl-V7/conf/layer.conf
====
# We have a conf and classes directory, add to BBPATH
BBPATH := "${BBPATH}:${LAYERDIR}"
# We have a recipes directory, add to BBFILES
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
BBFILE_COLLECTIONS += "dl-qemux86"
BBFILE_PATTERN_dl-qemux86 := "^${LAYERDIR}/"
BBFILE_PRIORITY_dl-qemux86 = "6"
=====
Thank you.
Regards,
Insop
- ref:
1. sched_deadline:
https://events.linuxfoundation.org/events/linuxcon-europe/song
2. sched_deadline:
http://events.linuxfoundation.org/images/stories/slides/elc2013_kobayashi.pdf?a
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
