Home
last modified time | relevance | path

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

123456

/linux/tools/memory-model/
H A 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 *)
H A Dlinux-kernel.cat51 * 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/tools/memory-model/Documentation/
H A 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 …]
H A Drecipes.txt532 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
H A Dglossary.txt123 Happens-Before (hb): A relation between two accesses in which LKMM
125 detail, please see the "THE HAPPENS-BEFORE RELATION: hb"
/linux/Documentation/ABI/testing/
H A 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/include/linux/
H A Dcpufreq.h121 * This indicates if the relation flag CPUFREQ_RELATION_E can be
305 /* relation flags */
357 unsigned int relation); /* Deprecated */
622 unsigned int relation);
625 unsigned int relation);
789 unsigned int max, unsigned int relation);
1062 unsigned int relation) in cpufreq_frequency_table_target() argument
1065 (relation & CPUFREQ_RELATION_E); in cpufreq_frequency_table_target()
1069 relation &= ~CPUFREQ_RELATION_E; in cpufreq_frequency_table_target()
1073 max, relation); in cpufreq_frequency_table_target()
[all …]
/linux/Documentation/devicetree/bindings/iommu/
H A 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/Documentation/translations/zh_CN/cpu-freq/
H A Dcpu-drivers.rst174 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 Dcpu-drivers.rst174 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/s390/block/
H A Ddasd_devmap.c35 * dasd_devmap_t is used to store the features and the relation
604 dev_warn(&device->cdev->dev, "Unable to query copy relation status\n"); in dasd_devmap_get_pprc_status()
613 dev_warn(&device->cdev->dev, "Error during copy relation status query\n"); in dasd_devmap_get_pprc_status()
648 * check the consistency of a specified copy relation by checking
673 dev_warn(&device->cdev->dev, "Device not part of a copy relation\n"); in dasd_devmap_check_copy_relation()
709 * the current device has to be part of the copy relation of all in dasd_devmap_check_copy_relation()
726 "Copy pair relation does not contain device: %s\n", in dasd_devmap_check_copy_relation()
736 /* delete device from copy relation entry */
755 * read all required information for a copy relation setup and setup the device
787 dev_err(&cdev->dev, "Copy relation not enabled on storage server\n"); in dasd_devmap_set_device_copy_relation()
[all …]
/linux/rust/kernel/
H A Dcpufreq.rs79 pub enum Relation { enum
88 impl Relation { impl
102 impl From<Relation> for u32 {
104 fn from(rel: Relation) -> Self { in from()
106 Relation::Low(e) => (CPUFREQ_RELATION_L, e), in from()
107 Relation::High(e) => (CPUFREQ_RELATION_H, e), in from()
108 Relation::Close(e) => (CPUFREQ_RELATION_C, e), in from()
779 fn target(_policy: &mut Policy, _target_freq: u32, _relation: Relation) -> Result { in target()
1204 relation: c_uint, in target_callback()
1210 T::target(policy, target_freq, Relation::new(relation)?).map(|()| 0) in target_callback()
/linux/Documentation/cpu-freq/
H A Dcpu-drivers.rst180 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/devicetree/bindings/dma/
H A Dsocionext,uniphier-xdmac.yaml37 relation to the device to use the DMA controller.
/linux/Documentation/devicetree/bindings/thermal/
H A Dgeneric-adc-thermal.yaml35 Lookup table to map the relation between ADC value and temperature.
/linux/Documentation/driver-api/surface_aggregator/
H A 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/tools/memory-model/litmus-tests/
H A 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/drivers/cpufreq/
H A Dcpufreq-nforce2.c245 * @relation: how that frequency relates to achieved frequency
251 unsigned int target_freq, unsigned int relation) in nforce2_target() argument
/linux/Documentation/usb/
H A Dmass-storage.rst27 relation to mass storage function (or MSF) and different gadgets
213 Relation to file storage gadget
/linux/Documentation/arch/powerpc/
H A Dvcpudispatch_stats.rst39 The final 3 numbers represent statistics in relation to the home node of
/linux/Documentation/devicetree/bindings/virtio/
H A Dpci-iommu.yaml15 device tree statically describes the relation between IOMMU and DMA
/linux/Documentation/hwmon/
H A Dstpddc60.rst37 The vout under- and over-voltage limits are set in relation to the commanded
/linux/kernel/futex/
H A Dpi.c168 * hb -> futex_q, relation
169 * futex_q -> pi_state, relation
182 * p->pi_state_list -> pi_state->list, relation
183 * pi_mutex->owner -> pi_state->owner, relation
787 * drop hb->lock since the caller owns the hb -> futex_q relation. in __fixup_pi_state_owner()
/linux/Documentation/userspace-api/media/v4l/
H A Daudio.rst22 The relation of video and audio connectors is defined in the
/linux/drivers/mfd/
H A D88pm80x.c39 * need to use this global variable to maintain the relation between

123456