| /linux-5.19.10/Documentation/filesystems/ ! |
| D | directory-locking.rst | 25 4) rename() that is _not_ cross-directory. Locking rules: caller locks
43 6) cross-directory rename. The trickiest in the whole bunch. Locking
74 (1) if object removal or non-cross-directory rename holds lock on A and
76 acquire the lock on B. (Proof: only cross-directory rename can change
79 (2) if cross-directory rename holds the lock on filesystem, order will not
80 change until rename acquires all locks. (Proof: other cross-directory
104 Any contended object is either held by cross-directory rename or
106 operation other than cross-directory rename. Then the lock this operation
109 It means that one of the operations is cross-directory rename.
112 own descendent. Moreover, there is exactly one cross-directory rename
[all …]
|
| /linux-5.19.10/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 | 18 highlights and cross-references. See below for details.
339 Highlights and cross-references
353 Name of a function parameter. (No cross-referencing, just formatting.)
356 Name of a constant. (No cross-referencing, just formatting.)
369 Name of an environment variable. (No cross-referencing, just formatting.)
381 Structure or union member reference. The cross-reference will be to the struct
391 No additional syntax is needed to cross-reference the functions and types
403 However, if you want custom text in the cross-reference link, that can be done
|
| /linux-5.19.10/drivers/media/tuners/ ! |
| D | r820t.c | 1549 struct r820t_sect_type cross[5]; /* (0,0)(0,Q-1)(0,I-1)(Q-1,0)(I-1,0) */ in r820t_imr_cross() local
1564 cross[i].gain_x = reg08; in r820t_imr_cross()
1565 cross[i].phase_y = reg09; in r820t_imr_cross()
1568 cross[i].gain_x = reg08; /* 0 */ in r820t_imr_cross()
1569 cross[i].phase_y = reg09 + 1; /* Q-1 */ in r820t_imr_cross()
1572 cross[i].gain_x = reg08; /* 0 */ in r820t_imr_cross()
1573 cross[i].phase_y = (reg09 | 0x20) + 1; /* I-1 */ in r820t_imr_cross()
1576 cross[i].gain_x = reg08 + 1; /* Q-1 */ in r820t_imr_cross()
1577 cross[i].phase_y = reg09; in r820t_imr_cross()
1580 cross[i].gain_x = (reg08 | 0x20) + 1; /* I-1 */ in r820t_imr_cross()
[all …]
|
| /linux-5.19.10/tools/testing/ktest/examples/ ! |
| D | crosstests.conf | 33 OUTPUT_DIR = ${THIS_DIR}/cross-compile
47 LOG_FILE = ${OUTPUT_DIR}/cross.log
214 BUILD_TARGET = cross
|
| D | README | 13 cross compilers from:
|
| /linux-5.19.10/drivers/usb/typec/mux/ ! |
| D | Kconfig | 16 tristate "Pericom PI3USB30532 Type-C cross switch driver"
19 Say Y or M if your system has a Pericom PI3USB30532 Type-C cross
|
| /linux-5.19.10/drivers/net/ethernet/intel/ ! |
| D | Kconfig | 79 bool "Support HW cross-timestamp on PCH devices"
83 Say Y to enable hardware supported cross-timestamping on PCH
84 devices. The cross-timestamp is available through the PTP clock
85 driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE).
331 bool "Support HW cross-timestamp on platforms with PTM support"
335 Say Y to enable hardware supported cross-timestamping on platforms
336 with PCIe PTM support. The cross-timestamp is available through
337 the PTP clock driver precise cross-timestamp ioctl
|
| /linux-5.19.10/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
|
| /linux-5.19.10/arch/parisc/ ! |
| D | Makefile | 45 CROSS32_COMPILE := $(call cc-cross-prefix, \
55 CROSS_COMPILE := $(call cc-cross-prefix, \
|
| /linux-5.19.10/tools/memory-model/ ! |
| D | lock.cat | 11 include "cross.cat"
96 with rfe-lf from cross(all-possible-rfe-lf)
116 with rfe-ru from cross(all-possible-rfe-ru)
|
| /linux-5.19.10/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;
|
| /linux-5.19.10/scripts/ ! |
| D | Makefile.compiler | 12 cc-cross-prefix = $(firstword $(foreach c, $(1), \
|
| /linux-5.19.10/Documentation/userspace-api/media/v4l/ ! |
| D | pixfmt-y12i.rst | 27 pixels cross the byte boundary and have a ratio of 3 bytes for each
|
| /linux-5.19.10/arch/ia64/scripts/ ! |
| D | toolchain-flags | 23 warning: your linker cannot handle cross-segment segment-relative relocations.
|
| /linux-5.19.10/samples/bpf/ ! |
| D | README.rst | 88 In order to cross-compile, say for arm64 targets, export CROSS_COMPILE and ARCH
91 build samples for the cross target::
|
| /linux-5.19.10/Documentation/admin-guide/hw-vuln/ ! |
| 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
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
|
| /linux-5.19.10/arch/m68k/ ! |
| D | Makefile | 19 CROSS_COMPILE := $(call cc-cross-prefix, \
|
| /linux-5.19.10/drivers/isdn/mISDN/ ! |
| D | Kconfig | 21 cross connecting of bchannels, conferencing, dtmf decoding,
|
| /linux-5.19.10/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,
|
| /linux-5.19.10/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
|
| /linux-5.19.10/arch/arc/ ! |
| D | Makefile | 9 CROSS_COMPILE := $(call cc-cross-prefix, arc-linux- arceb-linux-)
|
| /linux-5.19.10/arch/loongarch/ ! |
| D | Makefile | 28 …CROSS_COMPILE := $(call cc-cross-prefix, $(tool-archpref)-linux- $(tool-archpref)-linux-gnu- $(t…
|
| /linux-5.19.10/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
|