Searched full:cross (Results 1 – 25 of 117) sorted by relevance
12345
| /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 | 23 highlights and cross-references. See below for details.
389 Highlights and cross-references
403 Name of a function parameter. (No cross-referencing, just formatting.)
406 Name of a constant. (No cross-referencing, just formatting.)
419 Name of an environment variable. (No cross-referencing, just formatting.)
431 Structure or union member reference. The cross-reference will be to the struct
438 Cross-referencing from reStructuredText
441 No additional syntax is needed to cross-reference the functions and types
453 However, if you want custom text in the cross-reference link, that can be done
|
| D | sphinx.rst | 309 Please note that there is no need to use ``c:func:`` to generate cross
312 ``function()`` into a cross reference if an index entry for the given
411 Cross-referencing
414 Cross-referencing from one documentation page to another can be done simply by
417 "Documentation/". For example, to cross-reference to this page, all the
435 For information on cross-referencing to kernel-doc functions or types, see
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 40 5. rename that is _not_ cross-directory. Locking rules:
53 6. cross-directory rename. The trickiest in the whole bunch. Locking rules:
110 step in cross-directory renames; we need to be careful when checking if
189 cross-directory rename of some sort.
191 There must be a cross-directory rename in the set; indeed,
200 more than one cross-directory rename among them. Without loss of
201 generality we can assume that T1 is the one doing a cross-directory
204 In other words, we have a cross-directory rename that locked
208 cross-directory rename does not get to locking any directories until it
214 cross-directory rename; parents first, then possibly their children.
[all …]
|
| /Documentation/sphinx/ |
| D | automarkup.py | 55 # Reserved C words that we should skip when cross-referencing
62 # pointless to try to cross-reference them and, as has been known
64 # to the creation of incorrect and confusing cross references. So
127 # Keep track of cross-reference lookups that failed so we don't have to
137 # In sphinx3 we can cross-reference to C macro and function, each one with its
150 # cross-referencing inside it first.
210 # cross-referencing inside it first.
241 # cross reference to that page
298 # avoid adding cross-references to functions that have been explicitly
|
| /Documentation/arch/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
183 protected against cross Hyper-Thread attacks because the Fill Buffer and
|
| /Documentation/admin-guide/hw-vuln/ |
| D | cross-thread-rsb.rst | 4 Cross-Thread Return Address Predictions
7 Certain AMD and Hygon processors are subject to a cross-thread return address
32 CVE-2022-27672 Cross-Thread Return Address Predictions
|
| D | index.rst | 21 cross-thread-rsb
|
| D | core-scheduling.rst | 16 A cross-HT attack involves the attacker and victim running on different Hyper
18 full mitigation of cross-HT attacks is to disable Hyper Threading (HT). Core
19 scheduling is a scheduler feature that can mitigate some (not all) cross-HT
181 Open cross-HT issues that core scheduling does not solve
219 The main use case for Core scheduling is mitigating the cross-HT vulnerabilities
|
| D | mds.rst | 57 Because the buffers are potentially shared between Hyper-Threads cross
153 other variants cannot be protected against cross Hyper-Thread attacks.
211 cross Hyper-Threads when entering idle states. Some XEON PHI variants allow
225 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
165 CPU is not vulnerable to cross-thread TAA attacks.
207 buffers. Cross-thread attacks are still
209 tsx=on tsx_async_abort=full,nosmt As above, cross-thread attacks on SMT
|
| /Documentation/kbuild/ |
| D | gcc-plugins.rst | 15 modules, cross-compilation and building in a separate directory.
95 Or on Fedora when using cross-compilers that include plugins::
106 Run gcc (native or cross-compiler) to ensure plugin headers are detected::
|
| D | llvm.rst | 35 to compile for the host target. For cross compiling::
83 Cross Compiling
87 typically contain all supported back ends, which can help simplify cross
116 ``CROSS_COMPILE`` is necessary when cross compiling and ``LLVM_IAS=0``
|
| /Documentation/admin-guide/perf/ |
| D | hisi-pmu.rst | 79 - 5'b01000: comes from L3C in the cross-die;
82 - 5'b01111: comes from the cross-die DDR;
83 - 5'b10000: comes from cross-socket DDR;
|
| /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 | dev-touch.rst | 27 conductors cross. Alternatively, Self Capacitance measures the signal from each
|
| /Documentation/translations/it_IT/process/ |
| D | submit-checklist.rst | 36 la cross-compilazione o altri.
38 4) Una buona architettura per la verifica della cross-compilazione è la ppc64
|
| /Documentation/process/ |
| D | submit-checklist.rst | 93 2) Builds on multiple CPU architectures by using local cross-compile tools
95 cross-compilation checking because it tends to use ``unsigned long`` for
|
| /Documentation/devicetree/bindings/media/ |
| D | microchip,csi2dc.yaml | 18 identifier, then converts the byte stream to a pixel stream into a cross
57 This is named 'pclk'. The second clock must be the cross domain clock,
|
| /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/sound/ |
| D | cs35l34.txt | 42 effect without waiting for a zero 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
|
12345