| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | attack_vector_controls.rst | 107 The cross-thread attack vector involves a malicious userspace program or
111 Many cross-thread attacks can only be mitigated if SMT is disabled, which will
114 If cross-thread mitigations are fully enabled ('auto,nosmt'), all mitigations
115 for cross-thread attacks will be enabled. SMT may be disabled depending on
118 If cross-thread mitigations are partially enabled ('auto'), mitigations for
119 cross-thread attacks will be enabled but SMT will not be disabled.
121 If cross-thread mitigations are disabled, no mitigations for cross-thread
127 *cross-thread mitigations default to partially enabled*
148 'auto' All attack vectors enabled, partial cross-thread mitigations.
149 'auto,nosmt' All attack vectors enabled, full cross-thread mitigations.
[all …]
|
| H A D | index.rst | 22 cross-thread-rsb
|
| H A 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
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | headers.rst | 15 :generate-cross-refs:
24 :generate-cross-refs:
33 :generate-cross-refs:
42 :generate-cross-refs:
|
| /linux/Documentation/doc-guide/ |
| H A 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
25 enums and defines and create cross-references to a Sphinx book.
36 included via ..parsed-literal block with cross-references for the
44 and enum ``symbol``, creating cross-references for all of them.
81 Creates an enriched version of a Kernel header file with cross-links
90 uAPI headers will create cross-reference links to the code.
121 Sets C *namespace* to be used during cross-reference generation. Can
156 It won't generate cross-references for ``PRIVATE``::
[all …]
|
| H A 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.)
423 Name of an environment variable. (No cross-referencing, just formatting.)
435 Structure or union member reference. The cross-reference will be to the struct
445 No additional syntax is needed to cross-reference the functions and types
457 However, if you want custom text in the cross-reference link, that can be done
|
| /linux/drivers/media/tuners/ |
| H A 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/tools/perf/Documentation/ |
| H A D | Build.txt | 78 libraries for multiple architectures on the same system and then cross-compile
93 configuration paths for cross building:
95 $ PKG_CONFIG_SYSROOT_DIR="/path/to/cross/build/sysroot" \
101 the library paths for cross compilation.
112 Specifying ARCH and CROSS_COMPILE for cross compilation:
|
| /linux/Documentation/filesystems/ |
| H A 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 …]
|
| /linux/tools/testing/ktest/examples/ |
| H A D | crosstests.conf | 33 OUTPUT_DIR = ${THIS_DIR}/cross-compile
47 LOG_FILE = ${OUTPUT_DIR}/cross.log
214 BUILD_TARGET = cross
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-header.rst | 10 :generate-cross-refs:
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-header.rst | 10 :generate-cross-refs:
|
| /linux/drivers/net/ethernet/intel/ |
| H A D | Kconfig | 82 bool "Support HW cross-timestamp on PCH devices"
86 Say Y to enable hardware supported cross-timestamping on PCH
87 devices. The cross-timestamp is available through the PTP clock
88 driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE).
346 bool "Support HW cross-timestamp on platforms with PTM support"
350 Say Y to enable hardware supported cross-timestamping on platforms
351 with PCIe PTM support. The cross-timestamp is available through
352 the PTP clock driver precise cross-timestamp ioctl
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | videodev.rst | 11 :generate-cross-refs:
|
| H A D | pixfmt-y12i.rst | 28 pixels cross the byte boundary and have a ratio of 3 bytes for each
|
| /linux/Documentation/userspace-api/media/rc/ |
| H A D | lirc-header.rst | 16 :generate-cross-refs:
|
| /linux/arch/parisc/ |
| H A D | Makefile | 47 CROSS32_COMPILE := $(call cc-cross-prefix, \
57 CROSS_COMPILE := $(call cc-cross-prefix, \
|
| /linux/Documentation/kbuild/ |
| H A 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::
|
| /linux/Documentation/arch/x86/ |
| H A 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
|
| /linux/drivers/virtio/ |
| H A D | Kconfig | 226 bool "Virtio RTC cross-timestamping using Arm Generic Timer"
230 This enables Virtio RTC cross-timestamping using the Arm Generic Timer.
232 cross-timestamp is available through the PTP clock driver precise
233 cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE2 aka
|
| /linux/tools/memory-model/ |
| H A D | lock.cat | 11 include "cross.cat"
110 with rfe-lf from cross(all-possible-rfe-lf)
131 with rf-ru from cross(all-possible-rf-ru)
|
| /linux/scripts/ |
| H A D | Makefile.compiler | 12 cc-cross-prefix = $(firstword $(foreach c, $(1), \
|
| /linux/samples/bpf/ |
| H A D | README.rst | 98 In order to cross-compile, say for arm64 targets, export CROSS_COMPILE and ARCH
101 build samples for the cross target::
|
| /linux/arch/m68k/ |
| H A D | Makefile | 19 CROSS_COMPILE := $(call cc-cross-prefix, \
|
| /linux/drivers/isdn/mISDN/ |
| H A D | Kconfig | 21 cross connecting of bchannels, conferencing, dtmf decoding,
|