| /linux/security/yama/ |
| H A D | yama_lsm.c | 117 struct ptrace_relation *relation; in yama_relation_cleanup() local 121 list_for_each_entry_rcu(relation, &ptracer_relations, node) { in yama_relation_cleanup() 122 if (relation->invalid) { in yama_relation_cleanup() 123 list_del_rcu(&relation->node); in yama_relation_cleanup() 124 kfree_rcu(relation, rcu); in yama_relation_cleanup() 144 struct ptrace_relation *relation, *added; in yama_ptracer_add() local 156 list_for_each_entry_rcu(relation, &ptracer_relations, node) { in yama_ptracer_add() 157 if (relation->invalid) in yama_ptracer_add() 159 if (relation->tracee == tracee) { in yama_ptracer_add() 160 list_replace_rcu(&relation->node, &added->node); in yama_ptracer_add() [all …]
|
| /linux/tools/memory-model/ |
| H A D | lock.cat | 68 * until after the co relation has been generated. 88 (* Utility macro to convert a single pair to a single-edge relation *) 89 let pair-to-relation p = p ++ 0 94 * Compute the relation containing these possible edges. 101 * Convert the possible-rfe-noncrit-lf relation for e 105 map pair-to-relation (possible-rfe-noncrit-lf e) 116 * Compute the relation containing these possible edges. 124 (* Convert the possible-rf-ru relation for e to a set of single edges *) 126 map pair-to-relation (possible-rf-ru e) 133 (* Final rf relation *)
|
| H A D | linux-kernel.cat | 51 * Note: The po-unlock-lock-po relation only passes the lock to the direct 107 * No fences needed here for prop because relation confined to one process. 176 * a single constraint on an "executes-before" relation, xb:
|
| /linux/Documentation/translations/zh_CN/cpu-freq/ |
| H A D | cpu-drivers.rst | 174 unsigned int relation. 180 - 如果 relation==CPUFREQ_REL_L,尝试选择一个高于或等于 target_freq 的 new_freq。("L代表 182 - 如果 relation==CPUFREQ_REL_H,尝试选择一个低于或等于 target_freq 的 new_freq。("H代表
|
| /linux/Documentation/translations/zh_TW/cpu-freq/ |
| H A D | cpu-drivers.rst | 174 unsigned int relation. 180 - 如果 relation==CPUFREQ_REL_L,嘗試選擇一個高於或等於 target_freq 的 new_freq。("L代表 182 - 如果 relation==CPUFREQ_REL_H,嘗試選擇一個低於或等於 target_freq 的 new_freq。("H代表
|
| /linux/drivers/cpufreq/ |
| H A D | cpufreq_ondemand.c | 38 unsigned int freq_next, unsigned int relation) in generic_powersave_bias_target() argument 57 policy->max, relation); in generic_powersave_bias_target() 64 relation & CPUFREQ_RELATION_E); in generic_powersave_bias_target() 67 relation & CPUFREQ_RELATION_E); in generic_powersave_bias_target()
|
| H A D | cpufreq.c | 504 unsigned int relation) in __resolve_freq() argument 513 idx = cpufreq_frequency_table_target(policy, target_freq, min, max, relation); in __resolve_freq() 2360 unsigned int relation) in __cpufreq_driver_target() argument 2368 policy->max, relation); in __cpufreq_driver_target() 2371 policy->cpu, target_freq, relation, old_target_freq); in __cpufreq_driver_target() 2389 relation &= ~CPUFREQ_RELATION_E; in __cpufreq_driver_target() 2391 return cpufreq_driver->target(policy, target_freq, relation); in __cpufreq_driver_target() 2403 unsigned int relation) in cpufreq_driver_target() argument 2407 return __cpufreq_driver_target(policy, target_freq, relation); in cpufreq_driver_target()
|
| H A D | cpufreq_governor.h | 170 unsigned int freq_next, unsigned int relation);
|
| H A D | virtual-cpufreq.c | 117 unsigned int relation) in virt_cpufreq_target() argument
|
| H A D | gx-suspmod.c | 373 unsigned int relation) in cpufreq_gx_target() argument
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-bdi | 39 writeout speed in relation to the other devices. 53 writeout speed in relation to the other devices. 94 writeout speed in relation to the other devices.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | explanation.txt | 331 The most important relation between events is program order (po). You 339 This is inherently a single-CPU relation; two instructions executing 343 po-loc is a sub-relation of po. It links two memory accesses when the 422 memory model cannot assume there is a fixed program order relation 430 We say that two events are linked by a dependency relation when the 545 The reads-from relation (rf) links a write event to a read event when 557 Usage of the rf relation implicitly assumes that loads will always 723 Just like the po relation, co is inherently an ordering -- it is not 725 just like with the rf relation, we distinguish between stores that 738 The from-reads relation (fr) can be a little difficult for people to [all …]
|
| H A D | recipes.txt | 532 based on the relation between the accesses linking successive CPUs in a 537 this type of relation. In formal memory-modeling texts, this 538 relation is called "reads-from" and is usually abbreviated "rf". 542 of relation. In formal memory-modeling texts, this relation is 547 write-to-write relation between the last access of CPU1() and 549 this relation is often called "coherence order" and is sometimes
|
| /linux/Documentation/cpu-freq/ |
| H A D | cpu-drivers.rst | 180 unsigned int target_frequency, unsigned int relation. 187 - if relation==CPUFREQ_REL_L, try to select a new_freq higher than or equal 189 - if relation==CPUFREQ_REL_H, try to select a new_freq lower than or equal
|
| /linux/Documentation/hwmon/ |
| H A D | stpddc60.rst | 37 The vout under- and over-voltage limits are set in relation to the commanded
|
| /linux/Documentation/arch/powerpc/ |
| H A D | vcpudispatch_stats.rst | 39 The final 3 numbers represent statistics in relation to the home node of
|
| H A D | dexcr.rst | 49 The possible 'which' and 'ctrl' values are as follows. Note there is no relation
|
| /linux/Documentation/tools/rtla/ |
| H A D | rtla-hwnoise.rst | 63 all noise that the tool observed, and the *% CPU Aval* is the relation
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | audio.rst | 23 The relation of video and audio connectors is defined in the
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| H A D | client.rst | 55 connection/relation to that controller. This can be done via the 103 setup provided through the parent-child relation, are preserved. If 328 notifier may be specified, which determines its order in relation to any
|
| /linux/rust/kernel/ |
| H A D | cpufreq.rs | 1205 relation: c_uint, in target_callback() 1211 T::target(policy, target_freq, Relation::new(relation)?).map(|()| 0) in target_callback()
|
| /linux/tools/memory-model/litmus-tests/ |
| H A D | README | 213 interleaving descriptions of the relation between a pair of consecutive 232 A from-read ("fre") relation links P0()'s third to P1()'s first
|
| /linux/Documentation/locking/ |
| H A D | lockstat.rst | 21 The graph below shows the relation between the lock functions and the various
|
| /linux/Documentation/scheduler/ |
| H A D | schedutil.rst | 7 All this assumes a linear relation between frequency and work capacity,
|
| /linux/fs/pstore/ |
| H A D | Kconfig | 126 6) PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in relation
|