| /kernel/linux/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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-cache.json | 1171 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 0",
1175 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1180 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 1",
1184 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1189 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 2",
1193 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1198 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 3",
1202 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1211 …redit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers t…
1220 …redit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers t…
[all …]
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | balance.rst | 29 regular memory requests by allocating one from the dma pool, instead
30 of incurring the overhead of regular zone balancing.
34 right ratio of dma and regular memory, it is quite possible that balancing
58 Note that if the size of the regular zone is huge compared to dma zone,
60 deciding whether to balance the regular zone. The first solution
68 fall back into regular zone. This also makes sure that HIGHMEM pages
|
| D | transhuge.rst | 15 can continue working on the regular pages or regular pte mappings.
18 regular pages should be gracefully allocated instead and mixed in
24 backed by regular pages should be relocated on hugepages
101 regular pmd from under you (split_huge_pmd can run in parallel to the
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | instrumented.h | 17 * instrument_read - instrument regular read access
21 * Instrument a regular read access. The instrumentation should be inserted
31 * instrument_write - instrument regular write access
35 * Instrument a regular write access. The instrumentation should be inserted
45 * instrument_read_write - instrument regular read-write access
49 * Instrument a regular write access. The instrumentation should be inserted
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/fs/ |
| D | fs_types.c | 33 * * DT_REG - Regular file
69 * * FT_REG_FILE - Regular file
97 * * DT_REG - Regular file
|
| /kernel/linux/linux-6.6/fs/ |
| D | fs_types.c | 33 * * DT_REG - Regular file
69 * * FT_REG_FILE - Regular file
97 * * DT_REG - Regular file
|
| /kernel/linux/linux-6.6/Documentation/hid/ |
| D | hidraw.rst | 146 for regular input reports, but allows the host to request the value of a
149 the regular device read() interface. The format of the buffer issued with this report
156 This is slower on most devices where a dedicated Out endpoint exists for regular
159 updates via the regular device write() interface. The format of the buffer issued
168 via a HIDIOCSOUTPUT request, or the regular device write() interface. The format
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/Documentation/bpf/ |
| D | bpf_prog_run.rst | 64 which means the semantics are not quite as straight-forward as the regular test
77 via the same trace points as for regular XDP programs.
80 the regular (non-live) mode. The XDP program will be executed as though the
108 immediately. If a packet ends up being passed to the regular networking stack
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/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
|