| /linux/security/yama/ |
| A D | yama_lsm.c | 119 struct ptrace_relation *relation; in yama_relation_cleanup() local
124 if (relation->invalid) { in yama_relation_cleanup()
125 list_del_rcu(&relation->node); in yama_relation_cleanup()
126 kfree_rcu(relation, rcu); in yama_relation_cleanup()
159 if (relation->invalid) in yama_ptracer_add()
163 kfree_rcu(relation, rcu); in yama_ptracer_add()
184 struct ptrace_relation *relation; in yama_ptracer_del() local
189 if (relation->invalid) in yama_ptracer_del()
193 relation->invalid = true; in yama_ptracer_del()
331 if (relation->invalid) in ptracer_exception_found()
[all …]
|
| /linux/tools/memory-model/ |
| 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 *)
|
| 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:
|
| /linux/include/linux/ |
| A D | cpufreq.h | 350 unsigned int relation); /* Deprecated */
615 unsigned int relation);
618 unsigned int relation);
774 unsigned int relation);
1021 unsigned int relation) in cpufreq_frequency_table_target() argument
1024 (relation & CPUFREQ_RELATION_E); in cpufreq_frequency_table_target()
1028 relation &= ~CPUFREQ_RELATION_E; in cpufreq_frequency_table_target()
1032 relation); in cpufreq_frequency_table_target()
1034 switch (relation) { in cpufreq_frequency_table_target()
|
| /linux/drivers/cpufreq/ |
| 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()
|
| 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()
|
| A D | cpufreq_ondemand.c | 61 unsigned int freq_next, unsigned int relation) in generic_powersave_bias_target() argument
79 index = cpufreq_frequency_table_target(policy, freq_next, relation); in generic_powersave_bias_target()
86 relation & CPUFREQ_RELATION_E); in generic_powersave_bias_target()
89 relation & CPUFREQ_RELATION_E); in generic_powersave_bias_target()
|
| 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()
2319 unsigned int relation) in __cpufreq_driver_target() argument
2326 target_freq = __resolve_freq(policy, target_freq, relation); in __cpufreq_driver_target()
2329 policy->cpu, target_freq, relation, old_target_freq); in __cpufreq_driver_target()
2347 relation &= ~CPUFREQ_RELATION_E; in __cpufreq_driver_target()
2349 return cpufreq_driver->target(policy, target_freq, relation); in __cpufreq_driver_target()
2361 unsigned int relation) in cpufreq_driver_target() argument
2367 ret = __cpufreq_driver_target(policy, target_freq, relation); in cpufreq_driver_target()
|
| A D | cpufreq_governor.h | 170 unsigned int freq_next, unsigned int relation);
|
| A D | sh-cpufreq.c | 82 unsigned int relation) in sh_cpufreq_target() argument
|
| A D | cpufreq-nforce2.c | 251 unsigned int target_freq, unsigned int relation) in nforce2_target() argument
|
| /linux/Documentation/translations/zh_CN/cpu-freq/ |
| 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代表
|
| /linux/Documentation/translations/zh_TW/cpu-freq/ |
| 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代表
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| A D | samsung,sysmmu.yaml | 23 System MMUs are in many to one relation with peripheral devices, i.e. single
26 device. The relation between a System MMU and the peripheral device needs to be
|
| /linux/Documentation/ABI/testing/ |
| 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/ |
| A D | explanation.txt | 767 Note that the fr relation is determined entirely by the rf and co
1023 cumul-fence relation. That is, if we have:
1047 "preserved program order") relation, which links the po-earlier
1102 includes address dependencies to loads in the ppo relation.
1427 The LKMM defines yet another relation connected to times of
1436 The propagates-before (pb) relation capitalizes on the special
1613 that this relation is "inverted": It links the end of the
1679 the strong-fence relation links events that are separated by an
1723 relation, and R is po-before the grace period S. Thus we have:
1918 relation). It also gives a way to tell which unlock matches a
[all …]
|
| 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
|
| /linux/Documentation/devicetree/bindings/dma/ |
| A D | socionext,uniphier-xdmac.yaml | 37 relation to the device to use the DMA controller.
|
| /linux/Documentation/devicetree/bindings/thermal/ |
| A D | generic-adc-thermal.yaml | 35 Lookup table to map the relation between ADC value and temperature.
|
| /linux/Documentation/core-api/ |
| 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.
|
| /linux/Documentation/cpu-freq/ |
| 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
|
| /linux/Documentation/hwmon/ |
| A D | stpddc60.rst | 37 The vout under- and over-voltage limits are set in relation to the commanded
|
| /linux/Documentation/devicetree/bindings/virtio/ |
| A D | pci-iommu.yaml | 15 device tree statically describes the relation between IOMMU and DMA
|
| /linux/Documentation/arch/powerpc/ |
| A D | vcpudispatch_stats.rst | 39 The final 3 numbers represent statistics in relation to the home node of
|
| /linux/Documentation/tools/rtla/ |
| A D | rtla-hwnoise.rst | 61 all noise that the tool observed, and the *% CPU Aval* is the relation
|