| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | tasks.rst | 4 Tasks title
7 Tasks are units of execution for BitBake. Recipes (``.bb`` files) use
8 tasks to complete configuring, compiling, and packaging software. This
9 chapter provides a reference of the tasks defined in the OpenEmbedded
12 Normal Recipe Build Tasks
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:bitbake-user-manual/bitbake-user-manual-metadata:tasks`" and
21 .. _ref-tasks-build:
27 tasks required to build a recipe.
[all …]
|
| /OK3568_Linux_fs/yocto/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 …]
|
| /OK3568_Linux_fs/kernel/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 | cgroups.rst | 45 tasks, and all their future children, into hierarchical groups with
50 A *cgroup* associates a set of tasks with a set of parameters for one
54 facilities provided by cgroups to treat groups of tasks in
67 cgroups. Each hierarchy is a partition of all tasks in the system.
81 tasks in each cgroup.
100 the division of tasks into cgroups is distinctly different for
102 hierarchy to be a natural division of tasks, without having to handle
103 complex combinations of tasks that would be present if several
114 tasks etc. The resource planning for this server could be along the
123 In addition (system tasks) are attached to topcpuset (so
[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.
|
| H A D | cpusets.rst | 44 Nodes to a set of tasks. In this document "Memory Node" refers to
47 Cpusets constrain the CPU and Memory placement of tasks to only
82 the available CPU and Memory resources amongst the requesting tasks.
139 - You can list all the tasks (by pid) attached to any cpuset.
148 - in sched.c migrate_live_tasks(), to keep migrating tasks within
184 - cpuset.sched_relax_domain_level: the searching range when migrating tasks
192 CPUs and Memory Nodes, and attached tasks, are modified by writing
200 on a system into related sets of tasks such that each set is constrained
206 the detailed placement done on individual tasks and memory regions
264 of the rate that the tasks in a cpuset are attempting to free up in
[all …]
|
| /OK3568_Linux_fs/buildroot/package/directfb/ |
| H A D | 0001-fix-missing-davinci-voodoo-header.patch | 76 + c64xTask *tasks;
94 +DFBResult davinci_c64x_tasks_init ( DavinciC64xTasks *tasks,
97 +DFBResult davinci_c64x_tasks_destroy( DavinciC64xTasks *tasks );
102 + DavinciC64xTasks *tasks,
191 +davinci_c64x_load_block__L( DavinciC64xTasks *tasks,
196 + c64xTask *task = &tasks->tasks[tasks->num_tasks];
198 + D_ASSERT( tasks->num_tasks < tasks->max_tasks );
206 + tasks->num_tasks++;
272 +davinci_c64x_put_idct_uyvy_16x16__L( DavinciC64xTasks *tasks,
277 + c64xTask *task = &tasks->tasks[tasks->num_tasks];
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/scheduler/ |
| H A D | sched-deadline.rst | 12 3. Scheduling Real-Time Tasks
22 5. Tasks CPU affinity
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
58 consistent with the guarantee (using the CBS[2,3] algorithm). Tasks are then
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
[all …]
|
| 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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Ada-Tasks.html | 17 <title>Debugging with GDB: Ada Tasks</title>
19 <meta name="description" content="Debugging with GDB: Ada Tasks">
20 <meta name="keywords" content="Debugging with GDB: Ada Tasks">
29 <link href="Ada-Tasks-and-Core-Files.html#Ada-Tasks-and-Core-Files" rel="next" title="Ada Tasks and…
64 <a name="Ada-Tasks"></a>
67 Next: <a href="Ada-Tasks-and-Core-Files.html#Ada-Tasks-and-Core-Files" accesskey="n" rel="next">Ada…
70 <a name="Extensions-for-Ada-Tasks"></a>
71 <h4 class="subsubsection">15.4.10.7 Extensions for Ada Tasks</h4>
74 <p>Support for Ada tasks is analogous to that for threads (see <a href="Threads.html#Threads">Threa…
78 <dd><a name="index-info-tasks"></a>
[all …]
|
| H A D | Ada-Tasks-and-Core-Files.html | 17 <title>Debugging with GDB: Ada Tasks and Core Files</title>
19 <meta name="description" content="Debugging with GDB: Ada Tasks and Core Files">
20 <meta name="keywords" content="Debugging with GDB: Ada Tasks and Core Files">
30 <link href="Ada-Tasks.html#Ada-Tasks" rel="previous" title="Ada Tasks">
64 <a name="Ada-Tasks-and-Core-Files"></a>
67 …Ravenscar Profile</a>, Previous: <a href="Ada-Tasks.html#Ada-Tasks" accesskey="p" rel="previous">A…
77 For instance, on x86-linux, the list of tasks is available, but task
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Ada-Tasks.html | 17 <title>Debugging with GDB: Ada Tasks</title>
19 <meta name="description" content="Debugging with GDB: Ada Tasks">
20 <meta name="keywords" content="Debugging with GDB: Ada Tasks">
29 <link href="Ada-Tasks-and-Core-Files.html#Ada-Tasks-and-Core-Files" rel="next" title="Ada Tasks and…
64 <a name="Ada-Tasks"></a>
67 Next: <a href="Ada-Tasks-and-Core-Files.html#Ada-Tasks-and-Core-Files" accesskey="n" rel="next">Ada…
70 <a name="Extensions-for-Ada-Tasks"></a>
71 <h4 class="subsubsection">15.4.10.7 Extensions for Ada Tasks</h4>
74 <p>Support for Ada tasks is analogous to that for threads (see <a href="Threads.html#Threads">Threa…
78 <dd><a name="index-info-tasks"></a>
[all …]
|
| H A D | Ada-Tasks-and-Core-Files.html | 17 <title>Debugging with GDB: Ada Tasks and Core Files</title>
19 <meta name="description" content="Debugging with GDB: Ada Tasks and Core Files">
20 <meta name="keywords" content="Debugging with GDB: Ada Tasks and Core Files">
30 <link href="Ada-Tasks.html#Ada-Tasks" rel="previous" title="Ada Tasks">
64 <a name="Ada-Tasks-and-Core-Files"></a>
67 …Ravenscar Profile</a>, Previous: <a href="Ada-Tasks.html#Ada-Tasks" accesskey="p" rel="previous">A…
77 For instance, on x86-linux, the list of tasks is available, but task
|
| /OK3568_Linux_fs/yocto/poky/documentation/overview-manual/ |
| H A D | concepts.rst | 37 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
38 section of the Yocto Project Development Tasks Manual.
52 a list of tasks from it, and then executing those tasks.
80 BitBake also tries to execute any dependent tasks first. So for example,
152 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
153 section of the Yocto Project Development Tasks Manual.
311 ":ref:`dev-manual/common-tasks:enabling your layer`"
312 section in the Yocto Project Development Tasks Manual.
411 ":ref:`dev-manual/common-tasks:creating your own layer`"
413 Yocto Project Development Tasks Manual. For a general discussion on
[all …]
|
| /OK3568_Linux_fs/kernel/kernel/rcu/ |
| H A D | tasks.h | 23 * Definition for a Tasks-RCU-like mechanism.
84 /* Track exiting tasks in order to allow them to be waited for. */
97 /* RCU tasks grace-period state for debugging. */
151 // Enqueue a callback for the specified flavor of Tasks RCU.
170 // Wait for a grace period for the specified flavor of Tasks RCU.
181 /* RCU-tasks kthread that detects grace periods and invokes callbacks. */
196 * one RCU-tasks grace period and then invokes the callbacks. in rcu_tasks_kthread()
243 /* Spawn RCU-tasks grace-period kthread. */
257 * Print any non-default Tasks RCU settings.
266 pr_info("\tTrampoline variant of Tasks RCU enabled.\n"); in rcu_tasks_bootup_oddness()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/livepatch/ |
| H A D | livepatch.rst | 98 transition state where tasks are converging to the patched state.
100 sequence occurs when a patch is disabled, except the tasks converge from
104 interrupts. The same is true for forked tasks: the child inherits the
108 safe to patch tasks:
111 tasks. If no affected functions are on the stack of a given task,
113 the tasks on the first try. Otherwise it'll keep trying
121 a) Patching I/O-bound user tasks which are sleeping on an affected
124 b) Patching CPU-bound user tasks. If the task is highly CPU-bound
128 3. For idle "swapper" tasks, since they don't ever exit the kernel, they
135 the second approach. It's highly likely that some tasks may still be
[all …]
|
| /OK3568_Linux_fs/yocto/poky/scripts/lib/ |
| H A D | buildstats.py | 83 …"""Read buildstat text file. fallback_end is an optional end time for tasks that are not recorded …
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()):
167 raise ValueError("Refusing to aggregate buildstats, set of tasks "
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)
[all …]
|
| /OK3568_Linux_fs/yocto/poky/scripts/lib/checklayer/cases/ |
| H A D | bsp.py | 58 Selecting a machine may only affect the signature of tasks that are specific
84 # Invert the tune -> [tasks] mapping.
86 for tune, tasks in tune2tasks.items():
87 for task in tasks:
98 # The output below is most useful when we start with tasks that are at
100 # those tasks differ, the rest also does.
102 # To get an ordering of tasks, we do a topological sort of the entire
105 # is not necessarily representative, but should be close enough. Tasks
134 tasks = tunes[tune]
135 # As for test_signatures it would be nicer to sort tasks
[all …]
|
| /OK3568_Linux_fs/kernel/kernel/livepatch/ |
| H A D | transition.c | 30 * "straggler" tasks which failed to transition in the first attempt.
46 * tasks even in userspace and idle.
87 * All tasks have transitioned to KLP_UNPATCHED so we can now in klp_complete_transition()
297 * on other methods (e.g., switching tasks at kernel exit). in klp_try_switch_task()
340 * Sends a fake signal to all non-kthread tasks with TIF_PATCH_PENDING set.
348 pr_notice("signaling remaining tasks\n"); in klp_send_signals()
369 * Send fake signal to all non-kthread tasks which are in klp_send_signals()
381 * Try to switch all remaining tasks to the target patch state by walking the
382 * stacks of sleeping tasks and looking for any to-be-patched or
386 * If any tasks are still stuck in the initial patch state, schedule a retry.
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/icecc-create-env/ |
| H A D | icecc-create-env_0.1.bb | 18 # Task 10907 (meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_install) (dependent Tasks ['qui…
19 …ipes-devtools/quilt/quilt-native_0.60.bb, do_populate_sysroot) (dependent Tasks ['quilt-native, do…
20 …ols/icecc-create-env/icecc-create-env-native_0.1.bb, do_patch) (dependent Tasks ['icecc-create-env…
21 …icecc-create-env/icecc-create-env-native_0.1.bb, do_configure) (dependent Tasks ['icecc-create-env…
22 …s/icecc-create-env/icecc-create-env-native_0.1.bb, do_compile) (dependent Tasks ['icecc-create-env…
23 …s/icecc-create-env/icecc-create-env-native_0.1.bb, do_install) (dependent Tasks ['icecc-create-env…
24 …reate-env/icecc-create-env-native_0.1.bb, do_populate_sysroot) (dependent Tasks ['icecc-create-env…
25 # Task 10910 (meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_configure) (dependent Tasks ['q…
26 # Task 10911 (meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_compile) (dependent Tasks ['qui…
|
| /OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-execution.rst | 14 execute single tasks, compile single recipe files, capture or clear
94 tasks. See the
100 recipes and tasks that are executed.
218 tasks that the recipe defines and a set of data consisting of keys and
219 values as well as dependency information about the tasks.
361 Each target BitBake builds consists of multiple tasks such as ``fetch``,
384 BitBake can now calculate exactly what tasks it needs to run and in what
386 :ref:`bitbake-user-manual/bitbake-user-manual-execution:executing tasks`
392 variable. BitBake continues to fork threads as long as there are tasks
393 ready to run, those tasks have all their dependencies met, and the
[all …]
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/ |
| H A D | runqueue.py | 4 Handles preparation and execution of a queue of tasks
77 # Index used to pair up potentially matching multiconfig tasks
87 Holds statistics on the tasks handled by the associated runQueue
138 Control the order tasks are scheduled in.
217 # Once tasks are running we don't need to worry about them again
226 # this is the case, otherwise the pressure limitation could result in no tasks
227 # being active and no new tasks started thereby, at times, breaking the scheduler.
231 # Filter out tasks that have a max number of threads that have been exceeded
302 heavier weighted tasks (tasks needed by the most other tasks) are run first.
331 running all tasks related to the same .bb file one after the after.
[all …]
|
| /OK3568_Linux_fs/yocto/poky/scripts/contrib/bb-perf/ |
| H A D | buildstats-plot.sh | 12 # * without -S: Produces a histogram listing top N recipes/tasks versus
15 # * -S: Produces a histogram listing tasks versus stats. In this case,
21 # 1. Top recipes' tasks taking into account utime
25 # 2. Tasks versus utime:stime
29 # 3. Tasks versus IO write_bytes:IO read_bytes
43 TASKS="compile:configure:fetch:install:patch:populate_lic:populate_sysroot:unpack"
58 -t tasks The tasks to be computed
59 (default: "$TASKS")
86 TASKS="$OPTARG"
120 $CD/buildstats.sh -b "$BS_DIR" -s "$STATS" -t "$TASKS" $RECIPE $ACCUMULATE -H > $OUTBUILDSTATS
|
| /OK3568_Linux_fs/yocto/poky/scripts/ |
| H A D | oe-check-sstate | 3 # Query which tasks will be restored from 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)
85 …d state, and lists the tasks that would be restored. Set BB_SETSCENE_ENFORCE=1 in the environment …
90 …ue', help='Use same TMPDIR for check (list will then be dependent on what tasks have executed prev…
|