tasks (full) in projects: openbmc - OpenGrok search results

Searched full:tasks (Results 1 – 25 of 1509) sorted by relevance

/openbmc/openbmc/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-user-manual/bitbake-user-manual-metadata:tasks`" and 21 .. _ref-tasks-build: 27 tasks required to build a recipe. [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 …]`
/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/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.
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. 102 the division of tasks into cgroups is distinctly different for 104 hierarchy to be a natural division of tasks, without having to handle 105 complex combinations of tasks that would be present if several 116 tasks etc. The resource planning for this server could be along the 125 In addition (system tasks) are attached to topcpuset (so [all …]
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 …]
/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/linux/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 …]
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 …]
H A D	sched-rt-group.rst	14 2.3 Basis for grouping tasks 44 multiple groups of realtime tasks, each group must be assigned a fixed portion 57 tasks (SCHED_OTHER). Any allocated run time not used will also be picked up by 72 The remaining CPU time will be used for user input and other tasks. Because 73 realtime tasks have explicitly allocated the CPU time they need to perform 74 their tasks, buffer underruns in the graphics or audio can be eliminated. 110 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away 111 realtime tasks will not lock up the machine but leave a little time to recover 120 bandwidth to the group before it will accept realtime tasks. Therefore you will 121 not be able to run realtime tasks as any user other than root until you have [all …]
/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/openbmc/poky/documentation/overview-manual/
H A D	concepts.rst	38 section of the Yocto Project Development Tasks Manual. 52 a list of tasks from it, and then executing those tasks. 78 BitBake also tries to execute any dependent tasks first. So for example, 150 section of the Yocto Project Development Tasks Manual. 308 section in the Yocto Project Development Tasks Manual. 400 Yocto Project Development Tasks Manual. For a general discussion on 573 cases, a repository is cloned or checked out. The :ref:`ref-tasks-fetch` task 650 :ref:`do_package_write_* <ref-tasks-package_write_deb>` 651 tasks to generate packages and place them into the package holding area 653 ":ref:`ref-tasks-package_write_deb`", [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/poky/meta/recipes-devtools/icecc-create-env/
H A D	icecc-create-env_0.1.bb	17 # Task 10907 (meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_install) (dependent Tasks ['qui… 18 …ipes-devtools/quilt/quilt-native_0.60.bb, do_populate_sysroot) (dependent Tasks ['quilt-native, do… 19 …ols/icecc-create-env/icecc-create-env-native_0.1.bb, do_patch) (dependent Tasks ['icecc-create-env… 20 …icecc-create-env/icecc-create-env-native_0.1.bb, do_configure) (dependent Tasks ['icecc-create-env… 21 …s/icecc-create-env/icecc-create-env-native_0.1.bb, do_compile) (dependent Tasks ['icecc-create-env… 22 …s/icecc-create-env/icecc-create-env-native_0.1.bb, do_install) (dependent Tasks ['icecc-create-env… 23 …reate-env/icecc-create-env-native_0.1.bb, do_populate_sysroot) (dependent Tasks ['icecc-create-env… 24 # Task 10910 (meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_configure) (dependent Tasks ['q… 25 # Task 10911 (meta/recipes-devtools/quilt/quilt-native_0.60.bb, do_compile) (dependent Tasks ['qui…
/openbmc/openbmc/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 …]
/openbmc/linux/Documentation/livepatch/
H A D	livepatch.rst	85 transition state where tasks are converging to the patched state. 87 sequence occurs when a patch is disabled, except the tasks converge from 91 interrupts. The same is true for forked tasks: the child inherits the 95 safe to patch tasks: 98 tasks. If no affected functions are on the stack of a given task, 100 the tasks on the first try. Otherwise it'll keep trying 108 a) Patching I/O-bound user tasks which are sleeping on an affected 111 b) Patching CPU-bound user tasks. If the task is highly CPU-bound 115 3. For idle "swapper" tasks, since they don't ever exit the kernel, they 122 the second approach. It's highly likely that some tasks may still be [all …]
/openbmc/openbmc/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 …]
/openbmc/openbmc/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…`
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: 102 help="Sort tasks", 110 help="Hide tasks shorter than SECS seconds", 118 help="Highlight tasks longer than SECS seconds (0 disabled)",`
/openbmc/openbmc/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
/openbmc/openbmc/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 …]
/openbmc/linux/kernel/livepatch/
H A D	transition.c	51 * "straggler" tasks which failed to transition in the first attempt. 67 * tasks even in userspace and idle. 108 * All tasks have transitioned to KLP_UNPATCHED so we can now in klp_complete_transition() 325 * on other methods (e.g., switching tasks at kernel exit). in klp_try_switch_task() 405 * Sends a fake signal to all non-kthread tasks with TIF_PATCH_PENDING set. 413 pr_notice("signaling remaining tasks\n"); in klp_send_signals() 434 * Send fake signal to all non-kthread tasks which are in klp_send_signals() 444 * Try to switch all remaining tasks to the target patch state by walking the 445 * stacks of sleeping tasks and looking for any to-be-patched or 449 * If any tasks are still stuck in the initial patch state, schedule a retry. [all …]
/openbmc/linux/kernel/rcu/
H A D	tasks.h	24 * struct rcu_tasks_percpu - Per-CPU component of definition for a Tasks-RCU-like mechanism. 34 * @rtp_blkd_tasks: List of tasks blocked as readers. 35 * @rtp_exit_list: List of tasks in the latter portion of do_exit(). 58 * struct rcu_tasks - Definition for a Tasks-RCU-like mechanism. 153 /* Track exiting tasks in order to allow them to be waited for. / 190 / RCU tasks grace-period state for debugging. */ 247 // Tasks RCU. Do not enqueue callbacks before this function is invoked. 343 // Enqueue a callback for the specified flavor of Tasks RCU. 417 // Wait for all in-flight callbacks for the specified RCU Tasks flavor. 627 // RCU-tasks kthread that detects grace periods and invokes callbacks. [all …]

12 3 4 5 6 7 8 9 10 >>...61

Project(s)

Full Search
Definition
Symbol
File Path
History
Type