Searched full:semantics (Results 1 – 25 of 602) sorted by relevance
12345678910>>...25
54 * Semantics: Host is done using BMI62 * Semantics: Host reads ATH6KL memory73 * Semantics: Host writes ATH6KL memory84 * Semantics: Causes ATH6KL to execute code95 * Semantics: Set Target application starting address104 * Semantics: Read a 32-bit Target SOC register.114 * Semantics: Write a 32-bit Target SOC register.126 * Semantics: Fetch the 4-byte Target information141 * Semantics: Install a ROM Patch.155 * Semantics: Uninstall a previously-installed ROM Patch,[all …]
9 # kconfig semantics which are documented here. One known practical implication11 # drivers if they share a common core requirement and use disjoint semantics to18 # A perhaps not so obvious implication of this is that, if semantics on these31 # due to the disjoint use of semantics on expressing each bell's relationship43 # problem consisted on matching semantics with newly introduced features.
645 b) Match dependency semantics:698 Work on kconfig is welcomed on both areas of clarifying semantics and on705 Kconfig should have at least clear and well defined semantics which also712 Semantics of Kconfig719 semantics is welcomed. One project deduced Kconfig semantics through721 the deduced semantics matches our intended Kconfig design goals.722 Another project formalized a denotational semantics of a core subset of725 Having well defined semantics can be useful for tools for practical727 express in boolean abstraction of the inferred semantics of Kconfig to731 The kismet tool, based on the semantics in [10]_, finds abuses of reverse[all …]
36 SEMANTICS63 Except for a successful test_and_set_bit_lock() which has ACQUIRE semantics,64 clear_bit_unlock() which has RELEASE semantics and test_bit_acquire which has65 ACQUIRE semantics.
86 Owner semantics90 semantics:140 rw_semaphore complies by default with the strict owner semantics, but there193 semantics:205 PREEMPT_RT kernel due to the PREEMPT_RT specific spinlock_t semantics.224 The semantics of spinlock_t change with the state of PREEMPT_RT.227 exactly the same semantics.233 based on rt_mutex which changes the semantics:250 PREEMPT_RT kernels preserve all other spinlock_t semantics:309 implementation, thus changing semantics:[all …]
75 Semantics section in Generic Mutex Subsystem91 These semantics are fully enforced when CONFIG DEBUG_MUTEXES is enabled.150 Unless the strict semantics of mutexes are unsuitable and/or the critical
23 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using25 * for O_DSYNC semantics now, but using the correct symbolic name for it.26 * This new value is used to request true Posix O_SYNC semantics. It is28 * new headers get at least O_DSYNC semantics on older kernels.
20 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using22 * for O_DSYNC semantics now, but using the correct symbolic name for it.23 * This new value is used to request true Posix O_SYNC semantics. It is25 * new headers get at least O_DSYNC semantics on older kernels.
24 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using26 * for O_DSYNC semantics now, but using the correct symbolic name for it.27 * This new value is used to request true Posix O_SYNC semantics. It is29 * new headers get at least O_DSYNC semantics on older kernels.
16 * - Acquire: Provides ACQUIRE semantics, _acquire suffix.17 * - Release: Provides RELEASE semantics, _release suffix.21 * semantics apply only to the load and RELEASE semantics only to the
13 The second cell indicates the triggering semantics, and may have a14 value of either 4 for level semantics, or 1 for edge semantics.
66 * semantics. This field should only be read by the thread which78 * Read by user-space with single-copy atomicity semantics. This106 * atomicity semantics. This field should only be updated by the136 * user-space with single-copy atomicity semantics. This field should144 * user-space with single-copy atomicity semantics. This field should
66 * semantics. This field should only be read by the thread which78 * Read by user-space with single-copy atomicity semantics. This106 * atomicity semantics. This field should only be updated by the152 * user-space with single-copy atomicity semantics. This field should160 * user-space with single-copy atomicity semantics. This field should
7 implementation of semantics specific to those data structures.15 semantics or APIs are made or implied here.30 Luckily, some restrictions which necessitated the use of BPF map semantics are33 and semantics more closely match those exposed to the rest of the kernel.40 Unless otherwise stated, examples and semantics below apply to both graph data50 for kfuncs, the API and semantics for these data structures can be evolved in116 obvious. The verifier could enforce the same semantics as for ``bpf_obj_drop``,
56 #define mpu_command_port base + 1 /* write semantics */57 #define mpu_status_port base + 1 /* read semantics */59 #define status_port base + 3 /* read semantics */60 #define control_port base + 3 /* write semantics */
21 * This operation is atomic and provides release barrier semantics.51 * This operation is atomic and provides acquire barrier semantics if68 * This operation is atomic and provides release barrier semantics.
14 * This operation is atomic and provides acquire barrier semantics if38 * This operation is atomic and provides release barrier semantics.
67 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using69 * for O_DSYNC semantics now, but using the correct symbolic name for it.70 * This new value is used to request true Posix O_SYNC semantics. It is72 * new headers get at least O_DSYNC semantics on older kernels.
28 guest and host to increase performance and provide semantics that are not68 Mapping /dev/fuse to virtqueues requires solving differences in semantics71 prioritize certain requests over others. Virtqueues have queue semantics and
12 5) Detailed semantics24 that got mounted recently. Shared subtree semantics provide the necessary203 Apart from the above semantics this feature provides the208 The above semantics allows a way to share mounts across240 5) Detailed semantics242 The section below explains the detailed semantics of358 5b) Bind semantics435 5c) Rbind semantics472 5d) Move semantics549 5e) Mount semantics[all …]
151 * This operation is atomic and provides acquire barrier semantics.165 * This operation is atomic and provides release barrier semantics.179 * It does provide release barrier semantics so it can be used to unlock186 * provide release semantics anyway.
164 follow standard semantics.190 follow standard semantics.199 follow standard semantics.216 follow standard semantics.226 follow standard semantics.388 follow standard semantics.421 follow standard semantics.452 standard semantics.545 per the standard semantics of the V4L2 control interface. The client may552 semantics of the V4L2 control interface. If the client needs to apply the
16 * - Operand supports fine grained load/store/load+store semantics19 * - DMB guarantees SMP as well as local barrier semantics
113 semantics. Using the relaxed read functions will provide significant292 architecture-specific modes, with a shared set of semantics.373 Like ioremap(), but explicitly requests non-posted write semantics. On some374 architectures and buses, ioremap() mappings have posted write semantics, which378 due to the posted write semantics, this is not the case with respect to other379 devices. ioremap_np() explicitly requests non-posted semantics, which means386 semantics and portable drivers should use an abstraction that automatically400 Using ioremap_np() for PCI BARs will at best result in posted write semantics,403 Note that non-posted write semantics are orthogonal to CPU-side ordering
