| /openbmc/openbmc/poky/bitbake/lib/bb/tests/ |
| H A D | runqueue.py | 45 tasks = []
49 tasks = [line.rstrip() for line in f]
52 return tasks
58 tasks = self.run_bitbakecmd(cmd, tempdir, sstatevalid)
60 self.assertEqual(set(tasks), set(expected))
68 tasks = self.run_bitbakecmd(cmd, tempdir, sstatevalid)
72 self.assertEqual(set(tasks), set(expected))
80 tasks = self.run_bitbakecmd(cmd, tempdir, sstatevalid)
83 self.assertEqual(set(tasks), set(expected))
91 tasks = self.run_bitbakecmd(cmd, tempdir, sstatevalid)
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | bblock.py | 24 def unlock_recipes(self, recipes=None, tasks=None): argument
28 if tasks:
29 cmd += " -t " + ",".join(tasks)
36 for task in tasks:
50 def lock_recipes(self, recipes, tasks=None): argument
52 if tasks:
53 cmd += " -t " + ",".join(tasks)
62 if tasks:
63 for task in tasks:
74 def modify_tasks(self, recipes, tasks): argument
[all …]
|
| H A D | bbtests.py | 255 tasks = re.findall(r'task\s+(do_\S+):', ret.output)
257 for task in tasks:
259 'Executed tasks were: %s' % (task, str(tasks)))
268 tasks = re.findall(r'task\s+(do_\S+):', ret.output)
270 for task in tasks:
272 'Executed tasks were: %s' % (task, str(tasks)))
276 tasks = re.findall(r'task\s+(do_\S+):', ret.output)
278 self.assertFalse(tasks, 'Tasks %s ran when they should not have' % (str(tasks)))
285 tasks = re.findall(r'task\s+(do_\S+):', ret.output)
287 for task in tasks:
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | tasks.rst | 8 tasks to complete configuring, compiling, and packaging software. This
9 chapter provides a reference of the tasks defined in the OpenEmbedded
15 The following sections describe normal tasks associated with building a
16 recipe. For more information on tasks and dependencies, see the
17 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:tasks`" and
21 .. _ref-tasks-build:
27 tasks required to build a recipe.
29 .. _ref-tasks-compile:
39 If no such file is found, the :ref:`ref-tasks-compile` task does nothing.
41 .. _ref-tasks-compile_ptest_base:
[all …]
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | freezer-subsystem.rst | 6 and stop sets of tasks in order to schedule the resources of a machine
9 whole. The cgroup freezer uses cgroups to describe the set of tasks to
11 a means to start and stop the tasks composing the job.
14 of tasks. The freezer allows the checkpoint code to obtain a consistent
15 image of the tasks by attempting to force the tasks in a cgroup into a
16 quiescent state. Once the tasks are quiescent another task can
18 quiesced tasks. Checkpointed tasks can be restarted later should a
19 recoverable error occur. This also allows the checkpointed tasks to be
21 to another node and restarting the tasks there.
24 and resuming tasks in userspace. Both of these signals are observable
[all …]
|
| H A D | cpuacct.rst | 5 The CPU accounting controller is used to group tasks using cgroups and
6 account the CPU usage of these groups of tasks.
9 group accumulates the CPU usage of all of its child groups and the tasks
17 visible at /sys/fs/cgroup. At bootup, this group includes all the tasks in
18 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup.
20 by this group which is essentially the CPU time obtained by all the tasks
27 # echo $$ > g1/tasks
38 user: Time spent by tasks of the cgroup in user mode.
39 system: Time spent by tasks of the cgroup in kernel mode.
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/builds/ |
| H A D | test_core_image_min.py | 52 tasks = Task.objects.filter(
59 for task in tasks:
73 tasks = Task.objects.filter(outcome=2).values('id', 'sstate_result')
75 for task in tasks:
86 tasks = Task.objects.filter(
92 for task in tasks:
106 tasks = Task.objects.filter(
110 for task in tasks:
121 tasks = Task.objects.filter(
125 for task in tasks:
[all …]
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 6 Core scheduling support allows userspace to define groups of tasks that can
8 group of tasks don't trust another), or for performance usecases (some
20 attacks. It allows HT to be turned on safely by ensuring that only tasks in a
35 Using this feature, userspace defines groups of tasks that can be co-scheduled
37 tasks that are not in the same group never run simultaneously on a core, while
42 well as admission and removal of tasks from created groups::
67 will be performed for all tasks in the task group of ``pid``.
77 Building hierarchies of tasks
87 Transferring a cookie between the current and other tasks is possible using
91 scheduling group and share it with already running tasks.
[all …]
|
| /openbmc/openbmc/poky/scripts/lib/ |
| H A D | buildstats.py | 126 def __init__(self, tasks=None): argument
127 self._tasks = tasks or []
159 self.tasks = {}
166 if set(self.tasks.keys()) != set(bsrecipe.tasks.keys()):
170 for taskname, taskdata in bsrecipe.tasks.items():
171 if not isinstance(self.tasks[taskname], BSTaskAggregate):
172 self.tasks[taskname] = BSTaskAggregate([self.tasks[taskname]])
173 self.tasks[taskname].append(taskdata)
188 num += len(recipe.tasks)
202 bsrecipe.tasks[task] = BSTask(data)
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | bblock.rst | 7 unless BitBake determines that specific tasks do not require rebuilding.
8 At startup, it computes a signature for all tasks, based on the task's input.
19 To prevent this, use ``bblock`` to lock specific tasks or recipes to
32 Locking tasks and recipes
43 Locking a recipe means locking all tasks of the recipe. If you need to
44 lock only particular tasks, use the `-t` option with a comma-separated
45 list of tasks::
50 Unlocking tasks and recipes
61 Unlocking a recipe means unlocking all tasks of the recipe. If you need to
62 unlock only particular tasks use the ``-t`` option with a comma-separated
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-blivet/python3-blivet/ |
| H A D | 0009-invoking-fsck-with-infinite-timeout.patch | 13 blivet/tasks/fsck.py | 2 +-
16 diff --git a/blivet/tasks/fsck.py b/blivet/tasks/fsck.py
18 --- a/blivet/tasks/fsck.py
19 +++ b/blivet/tasks/fsck.py
|
| H A D | 0010-invoking-mkfs-with-infinite-timeout.patch | 17 blivet/tasks/fsmkfs.py | 2 +-
20 diff --git a/blivet/tasks/fsmkfs.py b/blivet/tasks/fsmkfs.py
22 --- a/blivet/tasks/fsmkfs.py
23 +++ b/blivet/tasks/fsmkfs.py
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-design-CFS.rst | 19 1/nr_running speed. For example: if there are 2 tasks running, then it runs
26 is its actual runtime normalized to the total number of running tasks.
37 Small detail: on "ideal" hardware, at any time all tasks would have the same
38 p->se.vruntime value --- i.e., tasks would execute simultaneously and no task
44 up CPU time between runnable tasks as close to "ideal multitasking hardware" as
62 increasing value tracking the smallest vruntime among all tasks in the
67 The total number of running tasks in the runqueue is accounted through the
68 rq->cfs.load value, which is the sum of the weights of the tasks queued on the
71 CFS maintains a time-ordered rbtree, where all runnable tasks are sorted by the
73 As the system progresses forwards, the executed tasks are put into the tree
[all …]
|
| H A D | sched-deadline.rst | 43 that makes it possible to isolate the behavior of tasks between each other.
53 "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
65 Summing up, the CBS[2,3] algorithm assigns scheduling deadlines to tasks so
67 interference between different tasks (bandwidth isolation), while the EDF[1]
69 to be executed next. Thanks to this feature, tasks that do not strictly comply
74 tasks in the following way:
128 Bandwidth reclaiming for deadline tasks is based on the GRUB (Greedy
132 The following diagram illustrates the state names for tasks handled by GRUB::
201 tasks in active state (i.e., ActiveContending or ActiveNonContending);
203 - Total bandwidth (this_bw): this is the sum of all tasks "belonging" to the
[all …]
|
| H A D | sched-util-clamp.rst | 12 of tasks. It was introduced in v5.3 release. The CGroup support was merged in
16 performance requirements and restrictions of the tasks, thus it helps the
35 One can tell the system (scheduler) that some tasks require a minimum
37 can tell the system that some tasks should be restricted from consuming too
45 dropped. It can also dynamically 'prime' up these tasks if it knows in the
56 Another example is in Android where tasks are classified as background,
58 resources background tasks are consuming by capping the performance point they
59 can run at. This constraint helps reserve resources for important tasks, like
63 background tasks to stay on the little cores which will ensure that:
65 1. The big cores are free to run top-app tasks immediately. top-app
[all …]
|
| /openbmc/linux/samples/bpf/ |
| H A D | tracex2_user.c | 85 static struct task tasks[1024]; in print_hist() local
93 if (memcmp(&tasks[i], &next_key, SIZE) == 0) in print_hist()
96 memcpy(&tasks[task_cnt++], &next_key, SIZE); in print_hist()
102 (__u32) tasks[i].pid_tgid, in print_hist()
103 tasks[i].comm, in print_hist()
104 (__u32) tasks[i].uid_gid); in print_hist()
105 print_hist_for_pid(fd, &tasks[i]); in print_hist()
|
| H A D | map_perf_test_user.c | 94 static int pre_test_lru_hash_lookup(int tasks) in pre_test_lru_hash_lookup() argument
295 typedef int (*pre_test_func)(int tasks);
315 static int pre_test(int tasks) in pre_test() argument
321 int ret = pre_test_funcs[i](tasks); in pre_test()
346 static void run_perf_test(int tasks) in run_perf_test() argument
348 pid_t pid[tasks]; in run_perf_test()
351 assert(!pre_test(tasks)); in run_perf_test()
353 for (i = 0; i < tasks; i++) { in run_perf_test()
363 for (i = 0; i < tasks; i++) { in run_perf_test()
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | bblock | 32 def getTaskSignatures(tinfoil, pn, tasks): argument
41 ret = tinfoil.run_command("getTaskSignatures", pn, tasks)
81 def bblockReset(lockfile, pns, package_archs, tasks): argument
99 if tasks and not any(element in line for element in tasks):
143 bblockReset(lockfile, global_args.pn, package_archs, global_args.tasks)
160 sigs = getTaskSignatures(tinfoil, [pn], global_args.tasks)
|
| H A D | oe-check-sstate | 26 def translate_virtualfns(tasks): argument
34 for task in tasks:
57 tasks = []
61 tasks.append(res.group(1))
62 outtasks = translate_virtualfns(tasks)
|
| H A D | buildstats-summary | 59 tasks = []
61 for task, stats in recipe.tasks.items():
68 tasks.append(t)
70 tasks.sort(key=lambda t: getattr(t, args.sort.name))
75 for t in tasks:
|
| /openbmc/linux/Documentation/power/ |
| H A D | freezing-of-tasks.rst | 2 Freezing of tasks
7 I. What is the freezing of tasks?
10 The freezing of tasks is a mechanism by which user space processes and some
18 and PF_FREEZER_SKIP (the last one is auxiliary). The tasks that have
30 All freezable tasks must react to that by calling try_to_freeze(), which
62 initiated a freezing operation, the freezing of tasks will fail and the entire
69 order to clear the PF_FROZEN flag for each frozen task. Then, the tasks that
73 Rationale behind the functions dealing with freezing and thawing of tasks
77 - freezes only userspace tasks
80 - freezes all tasks (including kernel threads) because we can't freeze
[all …]
|
| /openbmc/linux/drivers/gpu/drm/ |
| H A D | drm_flip_work.c | 117 struct list_head tasks; in flip_worker() local
123 INIT_LIST_HEAD(&tasks); in flip_worker()
125 list_splice_tail(&work->commited, &tasks); in flip_worker()
129 if (list_empty(&tasks)) in flip_worker()
132 list_for_each_entry_safe(task, tmp, &tasks, node) { in flip_worker()
|
| /openbmc/linux/kernel/sched/ |
| H A D | psi.c | 221 static bool test_state(unsigned int *tasks, enum psi_states state, bool oncpu) in test_state() argument
225 return unlikely(tasks[NR_IOWAIT]); in test_state()
227 return unlikely(tasks[NR_IOWAIT] && !tasks[NR_RUNNING]); in test_state()
229 return unlikely(tasks[NR_MEMSTALL]); in test_state()
231 return unlikely(tasks[NR_MEMSTALL] && in test_state()
232 tasks[NR_RUNNING] == tasks[NR_MEMSTALL_RUNNING]); in test_state()
234 return unlikely(tasks[NR_RUNNING] > oncpu); in test_state()
236 return unlikely(tasks[NR_RUNNING] && !oncpu); in test_state()
238 return tasks[NR_IOWAIT] || tasks[NR_MEMSTALL] || in test_state()
239 tasks[NR_RUNNING]; in test_state()
[all …]
|
| /openbmc/linux/tools/perf/scripts/python/ |
| H A D | sched-migration.py | 100 def __init__(self, tasks = [0], event = RunqueueEventUnknown()): argument
101 self.tasks = tuple(tasks)
107 if taskState(prev_state) == "R" and next in self.tasks \
108 and prev in self.tasks:
114 next_tasks = list(self.tasks[:])
115 if prev in self.tasks:
127 if old not in self.tasks:
129 next_tasks = [task for task in self.tasks if task != old]
134 if new in self.tasks:
137 next_tasks = self.tasks[:] + tuple([new])
[all …]
|
| /openbmc/openbmc/poky/meta-poky/conf/templates/default/ |
| H A D | conf-notes.txt | 17 - 'devtool' and 'recipetool' handle common recipe tasks
18 - 'bitbake-layers' handles common layer tasks
19 - 'oe-pkgdata-util' handles common target package tasks
|