Home
last modified time | relevance | path

Searched full:relation (Results 1 – 25 of 192) sorted by relevance

12345678

/linux-6.14.4/security/yama/
Dyama_lsm.c111 * yama_relation_cleanup - remove invalid entries from the relation list
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()
[all …]
/linux-6.14.4/tools/memory-model/
Dlock.cat68 * 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 *)
Dlinux-kernel.cat41 * 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-6.14.4/tools/memory-model/Documentation/
Dexplanation.txt15 7. THE PROGRAM ORDER RELATION: po AND po-loc
18 10. THE READS-FROM RELATION: rf, rfi, and rfe
19 11. CACHE COHERENCE AND THE COHERENCE ORDER RELATION: co, coi, and coe
20 12. THE FROM-READS RELATION: fr, fri, and fre
22 14. PROPAGATION ORDER RELATION: cumul-fence
26 18. THE PRESERVED PROGRAM ORDER RELATION: ppo
28 20. THE HAPPENS-BEFORE RELATION: hb
29 21. THE PROPAGATES-BEFORE RELATION: pb
56 through 12 (THE FROM_READS RELATION) describe the fundamental
328 THE PROGRAM ORDER RELATION: po AND po-loc
[all …]
Drecipes.txt528 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
Dglossary.txt123 Happens-Before (hb): A relation between two accesses in which LKMM
125 detail, please see the "THE HAPPENS-BEFORE RELATION: hb"
/linux-6.14.4/drivers/cpufreq/
Dfreq_table.c120 unsigned int relation) in cpufreq_table_index_unsorted() argument
135 pr_debug("request for target %u kHz (relation: %u) for cpu %u\n", in cpufreq_table_index_unsorted()
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()
Damd_freq_sensitivity.c41 unsigned int relation) in amd_powersave_bias_target() argument
95 relation & CPUFREQ_RELATION_E); in amd_powersave_bias_target()
Dcpufreq_ondemand.c61 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()
Dcpufreq-nforce2.c245 * @relation: how that frequency relates to achieved frequency
251 unsigned int target_freq, unsigned int relation) in nforce2_target() argument
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-class-bdi39 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-6.14.4/include/linux/
Dcpufreq.h123 * This indicates if the relation flag CPUFREQ_RELATION_E can be
298 /* relation flags */
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()
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.yaml23 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-6.14.4/Documentation/translations/zh_TW/cpu-freq/
Dcpu-drivers.rst175 unsigned int relation.
181 - 如果 relation==CPUFREQ_REL_L，嘗試選擇一個高於或等於 target_freq 的 new_freq。("L代表
183 - 如果 relation==CPUFREQ_REL_H，嘗試選擇一個低於或等於 target_freq 的 new_freq。("H代表
/linux-6.14.4/Documentation/translations/zh_CN/cpu-freq/
Dcpu-drivers.rst175 unsigned int relation.
181 - 如果 relation==CPUFREQ_REL_L，尝试选择一个高于或等于 target_freq 的 new_freq。("L代表
183 - 如果 relation==CPUFREQ_REL_H，尝试选择一个低于或等于 target_freq 的 new_freq。("H代表
/linux-6.14.4/drivers/s390/block/
Ddasd_devmap.c33 * dasd_devmap_t is used to store the features and the relation
602 dev_warn(&device->cdev->dev, "Unable to query copy relation status\n"); in dasd_devmap_get_pprc_status()
611 dev_warn(&device->cdev->dev, "Error during copy relation status query\n"); in dasd_devmap_get_pprc_status()
646 * check the consistency of a specified copy relation by checking
671 dev_warn(&device->cdev->dev, "Device not part of a copy relation\n"); in dasd_devmap_check_copy_relation()
707 * the current device has to be part of the copy relation of all in dasd_devmap_check_copy_relation()
724 "Copy pair relation does not contain device: %s\n", in dasd_devmap_check_copy_relation()
734 /* delete device from copy relation entry */
753 * read all required information for a copy relation setup and setup the device
785 dev_err(&cdev->dev, "Copy relation not enabled on storage server\n"); in dasd_devmap_set_device_copy_relation()
[all …]
/linux-6.14.4/Documentation/cpu-freq/
Dcpu-drivers.rst181 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-6.14.4/Documentation/core-api/
Drefcount-vs-atomic.rst35 program order (po) relation (on the same CPU). It guarantees that
70 a single CPU relation and provides no guarantees for other CPUs.
/linux-6.14.4/Documentation/devicetree/bindings/dma/
Dsocionext,uniphier-xdmac.yaml37 relation to the device to use the DMA controller.
/linux-6.14.4/Documentation/devicetree/bindings/thermal/
Dgeneric-adc-thermal.yaml35 Lookup table to map the relation between ADC value and temperature.
/linux-6.14.4/Documentation/driver-api/surface_aggregator/
Dclient.rst55 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-6.14.4/Documentation/usb/
Dmass-storage.rst27 relation to mass storage function (or MSF) and different gadgets
213 Relation to file storage gadget
/linux-6.14.4/tools/memory-model/litmus-tests/
DREADME213 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-6.14.4/Documentation/arch/powerpc/
Dvcpudispatch_stats.rst39 The final 3 numbers represent statistics in relation to the home node of
/linux-6.14.4/Documentation/devicetree/bindings/virtio/
Dpci-iommu.yaml15 device tree statically describes the relation between IOMMU and DMA

12345678