Hi Deitmar,
[ + eas-dev ]
On Sun, May 22, 2016 at 06:06:47PM +0100, Dietmar Eggemann wrote:
On 05/21/2016 06:25 AM, Leo Yan wrote:
On Fri, May 20, 2016 at 08:08:16PM +0100, Dietmar Eggemann wrote:
Hi Leo,
try the attached testcase in LISA which runs the wl's in '/tg_1/tg_11' You can create different tg level-hierarchies in rfc_tg.config if you wish.
08:05:17 DEBUG : sudo -- sh -c '/root/devlib-target/bin/shutils cgroups_run_into /tg_1/tg_11 '''/root/devlib-target/bin/rt-app /root/devlib-target/run_dir/06_pct_00.json''''
Very appreciate for the case.
I thought about this again and maybe you want to test task migration of a task running in a task group? This would make much more sense than only running task in a task group in case you want to test the pelt signals.
After enable EAS, I can see the task running in task group is migrated between different CPUs when task is waken up.
I added some functionality to rt-app which lets you restrict the cpu affinity of a task per phase of its run so you can create a task inside a task group which alternates between two cpus while running. This migration is done by the running task (so it's sched_setaffinity()->__set_cpus_allowed_ptr()->stop_one_cpu(..., migration_cpu_stop, ...)->__migrate_task()->move_queued_task()
So if you interested in this just ask me on eas-dev so I can share the rt-app functionality and a how-to build rt-app on the list for a broader audience.
Yes, this is another path we should test for task migration. So could you share this on mailing list? We also can consider to integrate this into rt-app's repo.
Thanks, Leo Yan