| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-driver-aspeed-uart-routing | 8 selected option marked by brackets "[]". The list of available options
25 will be marked by brackets "[]".
|
| /Linux-v6.6/lib/ |
| D | Kconfig.kcsan | 224 writes up to word size: conflicts between marked reads and plain
230 bool "Do not instrument marked atomic accesses"
233 Never instrument marked atomic accesses. This option can be used for
234 additional filtering. Conflicting marked atomic reads and plain
236 plain reads and marked writes to result in "unknown origin" reports.
238 races where at least one access is marked atomic will never be
242 accesses, conflicting marked atomic reads and plain writes will not
|
| /Linux-v6.6/Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-setup-link.rst | 41 enable/disable a link. Links marked with the ``IMMUTABLE`` link flag can
48 Only links marked with the ``DYNAMIC`` link flag can be enabled/disabled
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | ntfs3.rst | 38 this table marked with no it means default is without **no**.
70 will be marked as system immutable files.
92 - Forces the driver to mount partitions even if volume is marked dirty.
|
| D | automount-support.rst | 89 mountpoint will not be marked for expiration or unmounted.
91 If the mountpoint was not already marked for expiry at that time, an EAGAIN
94 Otherwise if it was already marked and it wasn't referenced, unmounting will
|
| /Linux-v6.6/security/yama/ |
| D | yama_lsm.c | 183 bool marked = false; in yama_ptracer_del() local
192 marked = true; in yama_ptracer_del()
197 if (marked) in yama_ptracer_del()
|
| /Linux-v6.6/Documentation/dev-tools/ |
| D | kcsan.rst | 206 KCSAN is aware of *marked atomic operations* (``READ_ONCE``, ``WRITE_ONCE``,
264 To detect data races between plain and marked accesses, KCSAN also annotates
265 marked accesses, but only to check if a watchpoint exists; i.e. KCSAN never
266 sets up a watchpoint on marked accesses. By never setting up watchpoints for
267 marked operations, if all accesses to a variable that is accessed concurrently
268 are properly marked, KCSAN will never trigger a watchpoint and therefore never
314 means reordering of marked accesses is not modeled.
317 instrumentation (no prefetching). Furthermore, marked accesses introducing
318 address or control dependencies do not require special handling (the marked
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | abi-obsolete.rst | 5 marked to be removed at some later point in time.
|
| D | abi-testing.rst | 13 be marked stable.
|
| /Linux-v6.6/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 30 A page is considered idle if it has not been accessed since it was marked idle
83 set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The
96 exceeding the dirty memory limit, it is not marked referenced.
104 When a page is marked idle, the Accessed bit must be cleared in all PTEs it is
|
| /Linux-v6.6/drivers/staging/pi433/ |
| D | TODO | 3 * Some missing data (marked with ###) needs to be added in the documentation
|
| /Linux-v6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c-pca-platform.txt | 16 is active low, it should be marked GPIO_ACTIVE_LOW.
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 67 2. Data-racy reads whose values are checked against marked reload.
104 fed into some operation that checks the full value against a later marked
211 It is important to comment marked accesses so that people reading your
222 if that concurrent access is marked with READ_ONCE(). In addition,
226 write is marked with data_race() or WRITE_ONCE().
297 this function can be marked __no_kcsan and the data_race() can be dropped:
343 Because foo is read locklessly, all accesses are marked. The purpose
464 Because foo is accessed locklessly, all accesses are marked. It does
513 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
| /Linux-v6.6/tools/testing/selftests/powerpc/pmu/sampling_tests/ |
| D | mmcra_thresh_marked_sample_test.c | 64 FAIL_IF(EV_CODE_EXTRACT(event.attr.config, marked) != in mmcra_thresh_marked_sample()
|
| /Linux-v6.6/Documentation/devicetree/bindings/spi/ |
| D | spi-clps711x.txt | 14 which is assumed to be in the same device tree, with and marked
|
| /Linux-v6.6/net/sched/ |
| D | sch_sfb.c | 79 u32 marked; /* ECN mark */ member
396 q->stats.marked++; in sfb_enqueue()
605 .marked = q->stats.marked, in sfb_dump_stats()
|
| /Linux-v6.6/Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 113 the page is broken down into 4K pages, which are then marked executable.
135 pages in the EPT are marked as non-executable.
137 broken down into 4K pages, which are then marked executable.
|
| /Linux-v6.6/Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 14 be marked that way in the devicetree.
|
| /Linux-v6.6/fs/bfs/ |
| D | Kconfig | 10 and corresponds to the slice marked as "STAND" in the UnixWare
|
| /Linux-v6.6/Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 37 buffers. These are all marked "empty", ready to receive data. This
47 flowing RX traffic, every descr behind it should be marked "full",
157 marked xa... which is "empty". Thus, from the OS point of view, there
163 The HW pointer is at descr 0. This descr is marked 0x4.. or "full".
165 halted processing. Notice that descrs 0 through 254 are all marked
|
| /Linux-v6.6/Documentation/livepatch/ |
| D | module-elf-format.rst | 110 Livepatch relocation sections must be marked with the SHF_RELA_LIVEPATCH
113 at patch module load time. These sections must also be marked with SHF_ALLOC,
166 characteristics. Notice that they are marked SHF_ALLOC ("A") so that they will
204 Livepatch symbols must be marked with SHN_LIVEPATCH so that the module
237 Livepatch symbols must have their section index marked as SHN_LIVEPATCH, so
|
| /Linux-v6.6/LICENSES/deprecated/ |
| D | Zlib | 25 2. Altered source versions must be plainly marked as such, and must not be
|
| /Linux-v6.6/tools/include/uapi/linux/ |
| D | pkt_sched.h | 280 __u32 marked; /* Marked packets */ member
380 __u32 marked; /* Marked packets */ member
757 __u32 marked; member
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | mtdnand.rst | 26 struct member has a short description which is marked with an [XXX]
33 The functions are marked with [XXX] identifiers in the short comment.
67 The struct members are marked with [XXX] identifiers in the comment. The
478 AG-AND chips this is mandatory, as they have no factory marked bad
479 blocks. They have factory marked good blocks. The marker pattern is
547 marked and identified by a pattern which is stored in the spare area
564 to be marked bad due to wear. The MTD interface function
577 about the one worn out block which should be marked bad. The version
957 developer. Each struct member has a short description which is marked
969 which is marked with an [XXX] identifier. See the chapter "Documentation
[all …]
|
| /Linux-v6.6/Documentation/dev-tools/kunit/ |
| D | running_tips.rst | 270 Test suites and cases can be marked with test attributes, such as speed of
277 Tests are marked with an attribute by including a ``kunit_attributes`` object
280 Test cases can be marked using the ``KUNIT_CASE_ATTR(test_name, attributes)``
297 Test suites can be marked with an attribute by setting the "attr" field in the
420 this could be marked as "slow" or "very_slow".
|
