| /kernel/linux/linux-5.10/security/yama/ |
| 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 …]
|
| /kernel/linux/linux-5.10/tools/memory-model/ |
| 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 *)
|
| D | linux-kernel.cat | 84 * No fences needed here for prop because relation confined to one process.
153 * a single constraint on an "executes-before" relation, xb:
|
| /kernel/linux/linux-5.10/drivers/cpufreq/ |
| 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()
|
| D | s3c24xx-cpufreq.c | 272 unsigned int relation) in s3c_cpufreq_target() argument
286 __func__, policy, target_freq, relation); in s3c_cpufreq_target()
290 relation); in s3c_cpufreq_target()
321 relation); in s3c_cpufreq_target()
|
| D | amd_freq_sensitivity.c | 41 unsigned int relation) in amd_powersave_bias_target() argument
|
| D | cpufreq_governor.h | 171 unsigned int freq_next, unsigned int relation);
|
| 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()
|
| D | sh-cpufreq.c | 83 unsigned int relation) in sh_cpufreq_target() argument
|
| D | cpufreq-nforce2.c | 251 unsigned int target_freq, unsigned int relation) in nforce2_target() argument
|
| D | cpufreq.c | 2190 unsigned int relation) in __cpufreq_driver_target() argument
2202 policy->cpu, target_freq, relation, old_target_freq); in __cpufreq_driver_target()
2218 return cpufreq_driver->target(policy, target_freq, relation); in __cpufreq_driver_target()
2223 index = cpufreq_frequency_table_target(policy, target_freq, relation); in __cpufreq_driver_target()
2231 unsigned int relation) in cpufreq_driver_target() argument
2237 ret = __cpufreq_driver_target(policy, target_freq, relation); in cpufreq_driver_target()
|
| D | gx-suspmod.c | 373 unsigned int relation) in cpufreq_gx_target() argument
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | cpufreq.h | 323 unsigned int relation); /* Deprecated */
598 unsigned int relation);
601 unsigned int relation);
753 unsigned int relation);
973 unsigned int relation) in cpufreq_frequency_table_target() argument
977 relation); in cpufreq_frequency_table_target()
979 switch (relation) { in cpufreq_frequency_table_target()
|
| /kernel/linux/linux-5.10/tools/memory-model/Documentation/ |
| D | explanation.txt | 330 The most important relation between events is program order (po). You
338 This is inherently a single-CPU relation; two instructions executing
342 po-loc is a sub-relation of po. It links two memory accesses when the
421 memory model cannot assume there is a fixed program order relation
429 We say that two events are linked by a dependency relation when the
492 The reads-from relation (rf) links a write event to a read event when
504 Usage of the rf relation implicitly assumes that loads will always
670 Just like the po relation, co is inherently an ordering -- it is not
672 just like with the rf relation, we distinguish between stores that
685 The from-reads relation (fr) can be a little difficult for people to
[all …]
|
| 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
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | thermal-generic-adc.txt | 16 to map the relation between ADC value and
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 36 writeout speed in relation to the other devices.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/virtio/ |
| D | iommu.txt | 5 device tree statically describes the relation between IOMMU and DMA
|
| /kernel/linux/linux-5.10/Documentation/cpu-freq/ |
| D | cpu-drivers.rst | 187 unsigned int target_frequency, unsigned int relation.
194 - if relation==CPUFREQ_REL_L, try to select a new_freq higher than or equal
196 - if relation==CPUFREQ_REL_H, try to select a new_freq lower than or equal
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/ |
| D | mmci.txt | 34 - st,neg-edge : data & command phase relation, generated on
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | vcpudispatch_stats.rst | 39 The final 3 numbers represent statistics in relation to the home node of
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | audio.rst | 22 The relation of video and audio connectors is defined in the
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 21 significant relation between partitions or some partition internally uses
|
| /kernel/linux/linux-5.10/tools/memory-model/litmus-tests/ |
| D | README | 205 interleaving descriptions of the relation between a pair of consecutive
224 A from-read ("fre") relation links P0()'s third to P1()'s first
|