Searched full:cross (Results 1 – 25 of 99) sorted by relevance
1234
| /Documentation/filesystems/ |
| D | directory-locking.rst | 25 4) rename() that is _not_ cross-directory. Locking rules: caller locks
45 6) cross-directory rename. The trickiest in the whole bunch. Locking
77 (1) if object removal or non-cross-directory rename holds lock on A and
79 acquire the lock on B. (Proof: only cross-directory rename can change
82 (2) if cross-directory rename holds the lock on filesystem, order will not
83 change until rename acquires all locks. (Proof: other cross-directory
107 Any contended object is either held by cross-directory rename or
109 operation other than cross-directory rename. Then the lock this operation
112 It means that one of the operations is cross-directory rename.
115 own descendent. Moreover, there is exactly one cross-directory rename
[all …]
|
| /Documentation/doc-guide/ |
| D | parse-headers.rst | 6 order to describe the userspace API and to generate cross-references
7 between the code and the documentation. Adding cross-references for
12 cross-references. It has to be called via Makefile, while building the
26 enums and defines and create cross-references to a Sphinx book.
65 included via ..parsed-literal block with cross-references for the
73 enums and enum symbols and create cross-references for all of them.
84 The \ **ignore**\ means that it won't generate cross references for a
92 The \ **replace**\ means that it will generate cross references for a
162 It won't generate cross-references for \ **PRIVATE**\ .
172 It will make the BAR1 and BAR2 enum symbols to cross reference the foo
|
| D | kernel-doc.rst | 17 highlights and cross-references. See below for details.
338 Highlights and cross-references
352 Name of a function parameter. (No cross-referencing, just formatting.)
355 Name of a constant. (No cross-referencing, just formatting.)
368 Name of an environment variable. (No cross-referencing, just formatting.)
380 Structure or union member reference. The cross-reference will be to the struct
387 Cross-referencing from reStructuredText
390 No additional syntax is needed to cross-reference the functions and types
402 However, if you want custom text in the cross-reference link, that can be done
|
| D | sphinx.rst | 246 Please note that there is no need to use ``c:func:`` to generate cross
249 ``function()`` into a cross reference if an index entry for the given
340 Cross-referencing
343 Cross-referencing from one documentation page to another can be done by passing
345 For example, to cross-reference to this page (the .rst extension is optional)::
354 For information on cross-referencing to kernel-doc functions or types, see
|
| /Documentation/sphinx/ |
| D | automarkup.py | 57 # Reserved C words that we should skip when cross-referencing
64 # pointless to try to cross-reference them and, as has been known
66 # to the creation of incorrect and confusing cross references. So
120 # In sphinx3 we can cross-reference to C macro and function, each one with its
213 # cross reference to that page
249 # avoid adding cross-references to functions that have been explicitly
|
| /Documentation/x86/ |
| D | mds.rst | 21 buffers are partitioned between Hyper-Threads so cross thread forwarding is
32 Hyper-Threads so cross thread leakage is possible.
39 exploited eventually. Load ports are shared between Hyper-Threads so cross
90 This does not protect against cross Hyper-Thread attacks except for MSBDS
91 which is only exploitable cross Hyper-thread when one of the Hyper-Threads
167 protected against cross Hyper-Thread attacks because the Fill Buffer and
|
| /Documentation/kbuild/ |
| D | llvm.rst | 35 Cross Compiling
39 which can help simplify cross compiling. ::
|
| D | gcc-plugins.rst | 15 modules, cross-compilation and building in a separate directory.
|
| /Documentation/networking/devlink/ |
| D | sja1105.rst | 46 - When VLANs span cross-chip topologies, the total
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-y12i.rst | 27 pixels cross the byte boundary and have a ratio of 3 bytes for each
|
| D | pixfmt-y10b.rst | 22 pixels cross the byte boundary and have a ratio of 5 bytes for each 4
|
| D | dev-touch.rst | 27 conductors cross. Alternatively, Self Capacitance measures the signal from each
|
| /Documentation/process/ |
| D | submit-checklist.rst | 31 3) Builds on multiple CPU architectures by using local cross-compile tools
34 4) ppc64 is a good architecture for cross-compilation checking because it
|
| /Documentation/translations/it_IT/process/ |
| D | submit-checklist.rst | 32 la cross-compilazione o altri.
34 4) Una buona architettura per la verifica della cross-compilazione è la ppc64
|
| /Documentation/admin-guide/hw-vuln/ |
| D | mds.rst | 57 Because the buffers are potentially shared between Hyper-Threads cross
161 other variants cannot be protected against cross Hyper-Thread attacks.
219 cross Hyper-Threads when entering idle states. Some XEON PHI variants allow
233 All MDS variants except MSBDS can be attacked cross Hyper-Threads. That
|
| D | tsx_async_abort.rst | 58 Because the buffers are potentially shared between Hyper-Threads cross
172 CPU is not vulnerable to cross-thread TAA attacks.
214 buffers. Cross-thread attacks are still
216 tsx=on tsx_async_abort=full,nosmt As above, cross-thread attacks on SMT
|
| /Documentation/trace/coresight/ |
| D | coresight-ect.rst | 4 CoreSight Embedded Cross Trigger (CTI & CTM).
13 The CoreSight Cross Trigger Interface (CTI) is a hardware device that takes
15 devices and interconnects them via the Cross Trigger Matrix (CTM) to other
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 8 title: ARM Coresight Cross Trigger Interface (CTI) device.
11 The CoreSight Embedded Cross Trigger (ECT) consists of CTI devices connected
13 a star topology via the Cross Trigger Matrix (CTM), which is not programmable.
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l34.txt | 42 effect without waiting for a zero cross.
|
| /Documentation/devicetree/bindings/clock/st/ |
| D | st,flexgen.txt | 5 - a clock cross bar (represented by a mux element)
32 | |->| | | | Cross | | | | | | |
|
| /Documentation/bpf/ |
| D | s390.rst | 202 - `Cross-compiling the kernel <https://wiki.gentoo.org/wiki/Embedded_Handbook/General/Cross-compili…
|
| /Documentation/sound/soc/ |
| D | pops-clicks.rst | 53 amplitude too quickly. It can be minimised by enabling the zero cross setting
|
| /Documentation/hwmon/ |
| D | k8temp.rst | 61 70 degrees C. The rule of the thumb -> CPU temperature should not cross
|
| /Documentation/sound/cards/ |
| D | maya44.rst | 148 cross-mixer from channels 1+2 to channels 3+4
150 cross-mixer from channels 3+4 to channels 1+2
|
| /Documentation/networking/ |
| D | ipvlan.rst | 102 anything. This is the traditional mode where slaves can cross-talk among
108 mode. i.e. port won't allow cross communication between slaves.
|
1234