From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Subject: CONFIG_LATENCYTOP fragment
Date: Tue, 22 Dec 2015 12:15:55 +0200 [thread overview]
Message-ID: <567922DB.8000202@reliableembeddedsystems.com> (raw)
Hi,
That's what I currently use:
meta-yocto-bsp = "heads/jethro:347347ad78c4c2502e83f2c2adff61f1ba8fed8b"
multi-v7-ml =
"heads/jethro-training-v4.1.x:e297c4f7c1baf38faecd6a2fcaa4cab0acea7dc1"
The idea is to use a stable kernel + multi_v7_defconfig and add to this
patches/configuration fragments.
I can add like this ikconfig, oprofile, posix_mqueues[0], but I don't
manage to get CONFIG_LATENCYTOP on top of multi_v7_defconfig.
In order to produce the config fragments I do:
bitbake linux-yocto-custom -c menuconfig
There I do my adjustments (disable SMP and enable LATENCYTOP)
bitbake linux-yocto-custom -c diffconfig, which spits out a
configuration fragment[1]
I did a new KTYPE[2][3] which seems to be picked up:
cat log.do_patch
DEBUG: Executing shell function do_patch
[INFO] validating against known patches (multi-v7-ml-not-smp-deb-meta)
mark --> multi-v7-ml-not-smp-deb.scc
mark --> not-smp-deb.scc
mark --> latencytop.scc
mark <-- latencytop.scc
mark <-- not-smp-deb.scc
mark <-- multi-v7-ml-not-smp-deb.scc
mark --> patch_marker.scc
mark <-- patch_marker.scc
mark -->
gen_tmpyocto-autobuilderyocto-autobuilderyocto-workercustom-jethro-multi-v7-core-image-minimal-sato-sdk-adtbuildbuildtmpworkmulti_v7_ml-poky-linux-gnueabilinux-yocto-custom4.4-rc5-custom-ml-not-smp-deb+gitAUTOINC+9f9499ae8e-r0_desc.scc
mark <--
gen_tmpyocto-autobuilderyocto-autobuilderyocto-workercustom-jethro-multi-v7-core-image-minimal-sato-sdk-adtbuildbuildtmpworkmulti_v7_ml-poky-linux-gnueabilinux-yocto-custom4.4-rc5-custom-ml-not-smp-deb+gitAUTOINC+9f9499ae8e-r0_desc.scc
mark --> multi-v7-ml-user-patches.scc
mark <-- multi-v7-ml-user-patches.scc
<=== processed .meta/cfg/scratch/multi-v7-ml-not-smp-deb-meta in 0 seconds
DEBUG: Shell function do_patch finished
... but SMP is still on.
What's the trick?
Regards,
Robert
[0]
https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.1.x/multi-v7-ml/recipes-kernel/linux/config/multi-v7-ml-base/features
[1]
https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.1.x/multi-v7-ml/recipes-kernel/linux/config/multi-v7-ml-base/features/latencytop
[2]
https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.1.x/multi-v7-ml/recipes-kernel/linux/config/multi-v7-ml-base/ktypes/not-smp-deb
[3]
https://github.com/RobertBerger/meta-mainline/blob/jethro-training-v4.1.x/multi-v7-ml/recipes-kernel/linux/config/multi-v7-ml-common/bsp/multi-v7-ml/multi-v7-ml-not-smp-deb.scc..."Software
is like sex, it's better when it's free"
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
reply other threads:[~2015-12-22 10:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=567922DB.8000202@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.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.