/openbmc/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 …]
|
/openbmc/qemu/target/sh4/ |
H A D | op_helper.c | 273 int relation; in helper_fcmp_eq_FT() local 276 relation = float32_compare(t0, t1, &env->fp_status); in helper_fcmp_eq_FT() 278 return relation == float_relation_equal; in helper_fcmp_eq_FT() 283 int relation; in helper_fcmp_eq_DT() local 286 relation = float64_compare(t0, t1, &env->fp_status); in helper_fcmp_eq_DT() 288 return relation == float_relation_equal; in helper_fcmp_eq_DT() 293 int relation; in helper_fcmp_gt_FT() local 296 relation = float32_compare(t0, t1, &env->fp_status); in helper_fcmp_gt_FT() 298 return relation == float_relation_greater; in helper_fcmp_gt_FT() 303 int relation; in helper_fcmp_gt_DT() local [all …]
|
/openbmc/linux/tools/memory-model/ |
H A D | lock.cat | 62 * until after the co relation has been generated. 87 * and then convert that relation to a set of single-edge relations. 90 let pair-to-relation p = p ++ 0 91 in map pair-to-relation ((LKW * {r}) & loc & ext) 111 let pair-to-relation p = p ++ 0 112 in map pair-to-relation ((((UL | IW) * {r}) & loc & ext) | 119 (* Final rf relation *)
|
H A D | linux-kernel.cat | 41 * Note: The po-unlock-lock-po relation only passes the lock to the direct 97 * No fences needed here for prop because relation confined to one process. 166 * a single constraint on an "executes-before" relation, xb:
|
/openbmc/linux/drivers/cpufreq/ |
H A D | freq_table.c | 120 unsigned int relation) in cpufreq_table_index_unsorted() argument 136 target_freq, relation, policy->cpu); in cpufreq_table_index_unsorted() 138 switch (relation) { in cpufreq_table_index_unsorted() 157 switch (relation) { in cpufreq_table_index_unsorted()
|
H A D | amd_freq_sensitivity.c | 41 unsigned int relation) in amd_powersave_bias_target() argument 95 relation & CPUFREQ_RELATION_E); in amd_powersave_bias_target()
|
H A D | cpufreq_ondemand.c | 62 unsigned int freq_next, unsigned int relation) in generic_powersave_bias_target() argument 80 index = cpufreq_frequency_table_target(policy, freq_next, relation); in generic_powersave_bias_target() 87 relation & CPUFREQ_RELATION_E); in generic_powersave_bias_target() 90 relation & CPUFREQ_RELATION_E); in generic_powersave_bias_target()
|
H A D | cpufreq.c | 537 unsigned int target_freq, unsigned int relation) in __resolve_freq() argument 546 idx = cpufreq_frequency_table_target(policy, target_freq, relation); in __resolve_freq() 2331 unsigned int relation) in __cpufreq_driver_target() argument 2338 target_freq = __resolve_freq(policy, target_freq, relation); in __cpufreq_driver_target() 2341 policy->cpu, target_freq, relation, old_target_freq); in __cpufreq_driver_target() 2359 relation &= ~CPUFREQ_RELATION_E; in __cpufreq_driver_target() 2361 return cpufreq_driver->target(policy, target_freq, relation); in __cpufreq_driver_target() 2373 unsigned int relation) in cpufreq_driver_target() argument 2379 ret = __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 | sh-cpufreq.c | 82 unsigned int relation) in sh_cpufreq_target() argument
|
/openbmc/linux/include/linux/ |
H A D | cpufreq.h | 339 unsigned int relation); /* Deprecated */ 612 unsigned int relation); 615 unsigned int relation); 791 unsigned int relation); 1038 unsigned int relation) in cpufreq_frequency_table_target() argument 1041 (relation & CPUFREQ_RELATION_E); in cpufreq_frequency_table_target() 1045 relation &= ~CPUFREQ_RELATION_E; in cpufreq_frequency_table_target() 1049 relation); in cpufreq_frequency_table_target() 1051 switch (relation) { in cpufreq_frequency_table_target()
|
/openbmc/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代表
|
/openbmc/linux/Documentation/translations/zh_CN/cpu-freq/ |
H A D | cpu-drivers.rst | 175 unsigned int relation. 181 - 如果 relation==CPUFREQ_REL_L,尝试选择一个高于或等于 target_freq 的 new_freq。("L代表 183 - 如果 relation==CPUFREQ_REL_H,尝试选择一个低于或等于 target_freq 的 new_freq。("H代表
|
/openbmc/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.
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | OPL-UK-3.0 | 63 obligations and liabilities in relation to the 86 (a) in relation to copyright, the Speaker of the House of 89 (b) in relation to database right, the Corporate
|
H A D | python-ldap | 8 author(s) shall not be liable for damages of any kind in relation to
|
H A D | CERN-OHL-1.1 | 39 …ding negligence), product liability or otherwise, arising in any way in relation to the Documentat… 40 …ity, costs, damages, fees and expenses, including claims by third parties, in relation to such use. 46 …nditions, or if the Licensee initiates legal action against Licensor in relation to this Licence. …
|
H A D | CERN-OHL-1.2 | 42 …relation to the Documentation, modified Documentation and/or the use, manufacture or distribution … 48 …nditions, or if the Licensee initiates legal action against Licensor in relation to this Licence. …
|
/openbmc/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 | 528 based on the relation between the accesses linking successive CPUs in a 533 this type of relation. In formal memory-modeling texts, this 534 relation is called "reads-from" and is usually abbreviated "rf". 538 of relation. In formal memory-modeling texts, this relation is 543 write-to-write relation between the last access of CPU1() and 545 this relation is often called "coherence order" and is sometimes
|
/openbmc/openbmc/meta-openpower/recipes-phosphor/host/ |
H A D | checkstop-monitor.bb | 27 # Install the override to set up a Conflicts relation
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/watchdog/ |
H A D | phosphor-watchdog_git.bb | 30 # Install the override to set up a Conflicts relation
|
/openbmc/linux/Documentation/core-api/ |
H A D | refcount-vs-atomic.rst | 35 program order (po) relation (on the same CPU). It guarantees that 70 a single CPU relation and provides no guarantees for other CPUs.
|
/openbmc/linux/Documentation/cpu-freq/ |
H A D | cpu-drivers.rst | 181 unsigned int target_frequency, unsigned int relation. 188 - if relation==CPUFREQ_REL_L, try to select a new_freq higher than or equal 190 - if relation==CPUFREQ_REL_H, try to select a new_freq lower than or equal
|
/openbmc/linux/Documentation/hwmon/ |
H A D | stpddc60.rst | 37 The vout under- and over-voltage limits are set in relation to the commanded
|