| /linux-5.10/arch/nds32/mm/ |
| D | alignment.c | 198 int imm, regular, load, len, addr_mode, idx_mode; in do_16() local
205 regular = 1; in do_16()
213 regular = 1; in do_16()
221 regular = 0; in do_16()
229 regular = 1; in do_16()
237 regular = 1; in do_16()
245 regular = 1; in do_16()
253 regular = 0; in do_16()
261 regular = 1; in do_16()
288 if (regular) in do_16()
[all …]
|
| /linux-5.10/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
79 Disable regular cpu hotplug
99 | Decrease cpu_hotplug_disabled, thereby enabling regular cpu hotplug
117 Regular CPU hotplug call path
149 regular CPU hotplug]
154 regular CPU hotplug and the suspend code path converge at the _cpu_down() and
156 in that during regular CPU hotplug, 0 is passed for the 'tasks_frozen'
207 a regular CPU hotplug operation, upon receiving the CPU_DEAD notification
259 Are there any known problems when regular CPU hotplug and suspend race
[all …]
|
| /linux-5.10/include/linux/ |
| D | instrumented.h | 16 * instrument_read - instrument regular read access
18 * Instrument a regular read access. The instrumentation should be inserted
31 * instrument_write - instrument regular write access
33 * Instrument a regular write access. The instrumentation should be inserted
46 * instrument_read_write - instrument regular read-write access
48 * Instrument a regular write access. The instrumentation should be inserted
|
| D | kcsan-checks.h | 185 * __kcsan_check_read - check regular read access for races
193 * __kcsan_check_write - check regular write access for races
202 * __kcsan_check_read_write - check regular read-write access for races
211 * kcsan_check_read - check regular read access for races
219 * kcsan_check_write - check regular write access for races
228 * kcsan_check_read_write - check regular read-write access for races
|
| /linux-5.10/tools/testing/selftests/bpf/progs/ |
| D | test_tcp_hdr_options.c | 90 struct tcp_opt regular; in store_option() member
103 write_opt.regular.kind = test_kind; in store_option()
104 write_opt.regular.len = option_total_len(test_opt->flags); in store_option()
105 write_opt.regular.data32 = 0; in store_option()
106 write_test_option(test_opt, write_opt.regular.data); in store_option()
107 err = bpf_store_hdr_opt(skops, &write_opt.regular, in store_option()
108 sizeof(write_opt.regular), 0); in store_option()
135 struct tcp_opt regular; in load_option() member
150 search_opt.regular.kind = test_kind; in load_option()
151 search_opt.regular.len = 0; in load_option()
[all …]
|
| /linux-5.10/Documentation/vm/ |
| D | balance.rst | 31 regular memory requests by allocating one from the dma pool, instead
32 of incurring the overhead of regular zone balancing.
36 right ratio of dma and regular memory, it is quite possible that balancing
60 Note that if the size of the regular zone is huge compared to dma zone,
62 deciding whether to balance the regular zone. The first solution
70 fall back into regular zone. This also makes sure that HIGHMEM pages
|
| D | transhuge.rst | 17 can continue working on the regular pages or regular pte mappings.
20 regular pages should be gracefully allocated instead and mixed in
26 backed by regular pages should be relocated on hugepages
108 regular pmd from under you (split_huge_pmd can run in parallel to the
|
| D | hmm.rst | 8 memory like GPU on board memory) into regular kernel path, with the cornerstone
36 driver and regular application memory (private anonymous, shared memory, or
37 regular file backed memory). From here on I will refer to this aspect as split
88 be considered the same as regular memory from the kernel point of view.
411 For now, device memory is accounted as any regular page in rss counters (either
418 device memory and not a lot of regular system memory and thus not freeing much
425 against same memory cgroup a regular page would be accounted to. This does
427 back from device memory to regular memory cannot fail because it would
|
| /linux-5.10/arch/x86/lib/ |
| D | kaslr.c | 5 * kernel and memory randomization is done early when the regular
7 * normally linked in the regular.
17 * When built for the regular kernel, several functions need to be stubbed out
18 * or changed to their regular kernel equivalent.
|
| /linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 6 ZAC compliant devices) as a regular block device without any write
40 metadata. It can also use a regular block device together with the zoned
41 block device; in that case the regular block device will be split logically
95 chunk, resulting in native random write performance similar to a regular
134 If a regular device is used in conjunction with the zoned block device,
139 are located at the start of the regular block device.
154 regular block device as the first device.
|
| /linux-5.10/Documentation/powerpc/ |
| D | pmu-ebb.rst | 46 concurrently with regular 'perf' commands, or any other perf events.
52 The exclusion between EBB events and regular events is implemented using the
55 If an EBB event and a regular event are both pinned, then whichever is enabled
118 regular event. If this is the last EBB event the PMU will be deconfigured and
125 The EBB handler is just regular userspace code, however it must be written in
|
| /linux-5.10/fs/ |
| D | fs_types.c | 33 * * DT_REG - Regular file
69 * * FT_REG_FILE - Regular file
97 * * DT_REG - Regular file
|
| /linux-5.10/Documentation/filesystems/ |
| D | squashfs.rst | 53 file type, i.e. regular file, directory, symbolic link, and block/char device
127 (regular file, directory, device, etc.), the inode contents and length
130 To further maximise compression, two types of regular file inode and
132 regular files and directories, and extended types where extra
168 Regular files consist of a sequence of contiguous compressed blocks, and/or a
187 Regular files can contain a fragment index which is mapped to a fragment
197 For space efficiency regular files store uid and gid indexes, which are
|
| D | dax.txt | 46 2. There exists a persistent flag FS_XFLAG_DAX that can be applied to regular
51 be inherited by all regular files and subdirectories that are subsequently
82 c) Changing the FS_XFLAG_DAX flag on existing regular files and
87 the change in behaviour for existing regular files may not occur
153 statx can be used to query S_DAX. NOTE that only regular files will ever have
|
| D | zonefs.rst | 11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
24 by allowing SSTables to be stored in a zone file similarly to a regular file
39 regular block device.
176 Zoned block devices may fail I/O requests for reasons similar to regular block
208 * Delayed write errors: similarly to regular block devices, if the device side
377 This aggregated conventional zone file can be used as a regular file::
395 the end of the file, similarly to any regular file system::
425 Size: 0 Blocks: 524288 IO Block: 4096 regular empty file
|
| /linux-5.10/drivers/net/slip/ |
| D | Kconfig | 23 allows you to use SLIP over a regular dial up shell connection. If
29 Internet connectivity if you have a regular dial up shell account on
56 allows you to use SLIP over a regular dial up shell connection, you
|
| /linux-5.10/arch/x86/include/asm/ |
| D | intel-family.h | 24 * - regular client parts
25 * _L - regular mobile parts
27 * _X - regular server parts
|
| /linux-5.10/arch/s390/include/asm/ |
| D | isc.h | 15 /* Regular I/O interrupts. */
16 #define IO_SCH_ISC 3 /* regular I/O subchannels */
|
| /linux-5.10/Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 69 (#) Regular file / blockdev, MAP_SHARED, PROT_READ / PROT_EXEC / PROT_WRITE
77 (#) Memory backed regular file, MAP_SHARED, PROT_READ / PROT_EXEC / PROT_WRITE
79 In the MMU case: As for ordinary regular files.
90 In the MMU case: As for ordinary regular files.
92 In the no-MMU case: As for memory backed regular files, but the
99 In the MMU case: As for ordinary regular files.
|
| /linux-5.10/fs/cramfs/ |
| D | Kconfig | 28 bool "Support CramFs image over a regular block device" if EXPERT
32 This option allows the CramFs driver to load data from a regular
|
| /linux-5.10/Documentation/input/devices/ |
| D | edt-ft5x06.rst | 43 mode regular events don't get delivered and the options described
54 device is not in regular operation mode.
|
| /linux-5.10/drivers/reset/ |
| D | reset-sunxi.c | 67 * our system, before we can even think of using a regular device
69 * The controllers that we can register through the regular device
|
| D | reset-socfpga.c | 71 * our system, before we can even think of using a regular device
73 * The controllers that we can register through the regular device
|
| /linux-5.10/arch/xtensa/kernel/ |
| D | vectors.S | 36 * indicate that the exception is either a double or a regular exception:
39 * < VALID_DOUBLE_EXCEPTION_ADDRESS: regular exception
79 s32i a0, a2, PT_DEPC # mark it as a regular exception
106 s32i a0, a2, PT_DEPC # mark it as a regular exception
170 * - Fixup entry conditions differ from regular exceptions:
254 * registers to return as if we were coming from a regular exception
272 s32i a0, a2, PT_DEPC # mark it as a regular exception
358 * registers to return as if we were coming from a regular exception
|
| /linux-5.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-strerror.txt | 6 tep_strerror - Returns a string describing regular errno and tep error number.
21 The _tep_ argument is trace event parser context. The _errnum_ is a regular
|