Searched full:semantics (Results  1 – 25 of 168) sorted by relevance
1234567
| /Documentation/ | 
| D | atomic_bitops.txt | 36 SEMANTICS 63 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 has 65 ACQUIRE semantics.
  | 
| /Documentation/kbuild/ | 
| D | Kconfig.recursion-issue-02 | 9 # kconfig semantics which are documented here. One known practical implication 11 # drivers if they share a common core requirement and use disjoint semantics to 18 # A perhaps not so obvious implication of this is that, if semantics on these 31 # due to the disjoint use of semantics on expressing each bell's relationship 43 # problem consisted on matching semantics with newly introduced features.
  | 
| D | kconfig-language.rst | 645   b) Match dependency semantics: 698 Work on kconfig is welcomed on both areas of clarifying semantics and on 705 Kconfig should have at least clear and well defined semantics which also 712 Semantics of Kconfig 719 semantics is welcomed. One project deduced Kconfig semantics through 721 the deduced semantics matches our intended Kconfig design goals. 722 Another project formalized a denotational semantics of a core subset of 725 Having well defined semantics can be useful for tools for practical 727 express in boolean abstraction of the inferred semantics of Kconfig to 731 The kismet tool, based on the semantics in [10]_, finds abuses of reverse [all …] 
 | 
| D | Kconfig.recursion-issue-01 | 42 # easy to understand. Note that matching semantics on the dependency on
  | 
| /Documentation/devicetree/bindings/mips/cavium/ | 
| D | ciu3.txt | 13   The second cell indicates the triggering semantics, and may have a 14   value of either 4 for level semantics, or 1 for edge semantics.
  | 
| D | cib.txt | 19    CIB.  The second cell specifies the triggering semantics of the
  | 
| /Documentation/locking/ | 
| D | locktypes.rst | 86 Owner semantics 90 semantics: 140 rw_semaphore complies by default with the strict owner semantics, but there 193 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 …] 
 | 
| D | mutex-design.rst | 75 Semantics  chapter 91 These semantics are fully enforced when CONFIG DEBUG_MUTEXES is enabled. 168 Unless the strict semantics of mutexes are unsuitable and/or the critical
  | 
| /Documentation/filesystems/ | 
| D | virtiofs.rst | 28 guest and host to increase performance and provide semantics that are not 68 Mapping /dev/fuse to virtqueues requires solving differences in semantics 71 prioritize certain requests over others.  Virtqueues have queue semantics and
  | 
| D | sharedsubtree.rst | 12 	5) Detailed semantics 24 that got mounted recently.  Shared subtree semantics provide the necessary 203 	Apart from the above semantics this feature provides the 208 		The above semantics allows a way to share mounts across 240 5) Detailed semantics 242 	The section below explains the detailed semantics of 358 5b) Bind semantics 435 5c) Rbind semantics 472 5d) Move semantics 549 5e) Mount semantics [all …] 
 | 
| /Documentation/bpf/ | 
| D | graph_ds_impl.rst | 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 are 33 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 data 50 for kfuncs, the API and semantics for these data structures can be evolved in 116 obvious. The verifier could enforce the same semantics as for ``bpf_obj_drop``,
  | 
| D | map_cgroup_storage.rst | 18 This document describes the usage and semantics of the 123 Semantics  chapter
  | 
| /Documentation/userspace-api/media/v4l/ | 
| D | dev-encoder.rst | 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 may 552 semantics of the V4L2 control interface. If the client needs to apply the
  | 
| D | ext-ctrls-codec-stateless.rst | 31     Semantics". For further documentation, refer to the above 176     Semantics". For further documentation, refer to the above 280     List Semantics". For further documentation, refer to the above 315     :ref:`h264`, section 7.4.3 "Slice Header Semantics". For further 410     section 7.4.3.2 "Prediction Weight Table Semantics". 1594 See section '7.3.1 Tx mode semantics' of the :ref:`vp9` specification for more details. 1806 See section '7.2 Uncompressed header semantics' of the :ref:`vp9` specification 1836 See section '7.2.7 Interpolation filter semantics' of the :ref:`vp9` specification 1863 See section '7.3.6 Frame reference mode semantics' of the :ref:`vp9` specification for more details. 1998 '7.2.8 Loop filter semantics' of the :ref:`vp9` specification for more details. [all …] 
 | 
| /Documentation/features/debug/debug-vm-pgtable/ | 
| D | arch-support.txt | 4 #         description:   arch supports pgtable tests for semantics compliance
  | 
| /Documentation/i2c/ | 
| D | summary.rst | 20 SMBus, but some SMBus protocols add semantics beyond what is required to 28 implement all the common SMBus protocol semantics or messages.
  | 
| /Documentation/admin-guide/LSM/ | 
| D | SafeSetID.rst | 56 spawning semantics in the application (e.g. by using a privileged helper program 58 number of semantics around process spawning that would be affected by this, such 64 that rely on certain process-spawning semantics in Linux.
  | 
| /Documentation/driver-api/ | 
| D | device-io.rst | 113 semantics. Using the relaxed read functions will provide significant 292 architecture-specific modes, with a shared set of semantics. 373 Like ioremap(), but explicitly requests non-posted write semantics. On some 374 architectures and buses, ioremap() mappings have posted write semantics, which 378 due to the posted write semantics, this is not the case with respect to other 379 devices. ioremap_np() explicitly requests non-posted semantics, which means 386 semantics and portable drivers should use an abstraction that automatically 400 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
  | 
| /Documentation/userspace-api/ | 
| D | iommufd.rst | 128   attaching a device to an IOAS object. This is compatible to the semantics of 182 explicitly imposing the group semantics in its uAPI as VFIO does. 203 change but better matches the IOMMUFD API semantics and easier to support new
  | 
| /Documentation/ABI/testing/ | 
| D | sysfs-class-led-trigger-pattern | 34 		Since different LED hardware can have different semantics of
  | 
| D | sysfs-firmware-ofw | 20 		filesystem support, and has largely the same semantics and
  | 
| /Documentation/arch/x86/ | 
| D | elf_auxvec.rst | 7 This document describes the semantics of the x86 auxiliary vectors.
  | 
| /Documentation/devicetree/bindings/powerpc/ | 
| D | sleep.yaml | 23   The semantics of what type of low power modes are possible are defined
  | 
| /Documentation/netlink/specs/ | 
| D | nftables.yaml | 1208       doc: Delete an existing table with destroy semantics (ignoring ENOENT errors). 1252       doc: Delete an existing chain with destroy semantics (ignoring ENOENT errors). 1310       doc: Delete an existing rule with destroy semantics (ignoring ENOENT errors). 1354       doc: Delete an existing set with destroy semantics (ignoring ENOENT errors). 1412       doc: Delete an existing set element with destroy semantics. 1470       doc: Delete an existing stateful object with destroy semantics. 1514       doc: Delete an existing flow table with destroy semantics.
  | 
| /Documentation/userspace-api/media/dvb/ | 
| D | ca-fopen.rst | 55 affect the semantics of the ``open()`` call itself. A device opened in
  | 
        1234567