| /linux/scripts/lib/kdoc/ |
| H A D | kdoc_re.py | 6 Regular expression ancillary classes.
8 Those help caching regular expressions and do matching for kernel-doc.
13 # Local cache for regular expressions
22 regular expressions and define sub at class init time.
24 Regular expressions can be cached via an argument, helping to speedup
40 Compile a regular expression and initialize internal vars.
50 Return the regular expression pattern.
56 Allows adding two regular expressions into one.
109 Finding nested delimiters is hard with regular expressions. It is
111 advanced regular expression
[all...] |
| /linux/Documentation/power/ |
| H A 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/tools/testing/selftests/bpf/progs/ |
| H A 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/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-cache.json | 1305 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 0",
1310 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1315 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 1",
1320 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1325 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 2",
1330 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1335 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 3",
1340 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1350 …redit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers t…
1360 …redit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers t…
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A 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/Documentation/driver-api/soundwire/ |
| H A D | bra.rst | 19 The regular control channel uses Column 0 and can only send/retrieve
52 (6) The regular read/write commands can be issued in parallel with
73 the paging registers used for the regular command/control
219 Concurrency between BRA and regular read/write
227 mutex for regular read/write and BRA is a show-stopper. Independent
241 "regular" read/writes in parallel with the command channel, and last
276 is available or not, and use a regular read-write command channel in
284 For regular audio transfers, the machine driver exposes a dailink
316 concept of multi-link aggregation allowed by regular DAI links.
|
| /linux/Documentation/arch/powerpc/ |
| H A 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/Documentation/devicetree/bindings/pinctrl/ |
| H A D | thead,th1520-pinctrl.yaml | 25 Pinconf is fairly regular except for a few pads in group 1 that either can't
97 description: Enable the regular 48kOhm pull-up
99 description: Enable the strong 2.1kOhm pull-up or regular 48kOhm pull-up
105 description: Enable the regular 44kOhm pull-down
|
| /linux/Documentation/hid/ |
| H A 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
|
| /linux/fs/ |
| H A D | fs_types.c | 33 * * DT_REG - Regular file
69 * * FT_REG_FILE - Regular file
97 * * DT_REG - Regular file
|
| /linux/Documentation/bpf/ |
| H A 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
|
| /linux/drivers/net/slip/ |
| H A 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/tools/perf/Documentation/ |
| H A D | perf-amd-ibs.txt | 39 IBS VS. REGULAR CORE PMU
43 no skid. Whereas the IP recorded by regular core PMU will have some skid
45 regular core PMU might not help for profiling with instruction level
47 question. On the other hand, regular core PMU has it's own advantages like
51 Three regular core PMU events are internally forwarded to IBS Op PMU when
|
| /linux/Documentation/admin-guide/mm/ |
| H A 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/arch/s390/include/asm/ |
| H A D | isc.h | 15 /* Regular I/O interrupts. */
16 #define IO_SCH_ISC 3 /* regular I/O subchannels */
|
| /linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | uncore-cache.json | 848 … from the Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL…
2620 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 0",
2625 …regular credits available for posting reads from the HA into the iMC. In order to send reads into…
2630 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 1",
2635 …regular credits available for posting reads from the HA into the iMC. In order to send reads into…
2640 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 2",
2645 …regular credits available for posting reads from the HA into the iMC. In order to send reads into…
2650 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 3",
2655 …regular credits available for posting reads from the HA into the iMC. In order to send reads into…
2665 …redit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers t…
[all …]
|
| /linux/io_uring/ |
| H A D | opdef.h | 16 /* hash wq insertion if file is a regular file */
18 /* unbound wq insertion if file is a non-regular file */
|
| /linux/include/linux/irqchip/ |
| H A D | arm-gic-v3-prio.h | 17 * GICV3_PRIO_IRQ is the PMR view of the priority of regular interrupts. This
18 * can be written to the PMR to mask regular IRQs.
|
| /linux/arch/xtensa/kernel/ |
| H A 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:
255 * registers to return as if we were coming from a regular exception
273 s32i a0, a2, PT_DEPC # mark it as a regular exception
364 * registers to return as if we were coming from a regular exception
|
| /linux/scripts/ |
| H A D | sphinx-pre-install | 370 check_missing_file(["/usr/share/fonts/noto-cjk/NotoSansCJK-Regular.ttc",
371 "/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc",
372 "/usr/share/fonts/opentype/noto/NotoSerifCJK-Regular.ttc"],
444 check_missing_file(["/usr/share/fonts/google-noto-cjk/NotoSansCJK-Regular.ttc",
445 "/usr/share/fonts/google-noto-sans-cjk-fonts/NotoSansCJK-Regular.ttc"],
547 check_missing_file(["/usr/share/fonts/google-noto-cjk/NotoSansCJK-Regular.ttc",
548 "/usr/share/fonts/TTF/NotoSans-Regular.ttf"],
580 check_missing_file(["/usr/share/fonts/noto-cjk/NotoSansCJK-Regular.ttc"],
606 check_missing_file(["/usr/share/fonts/noto-cjk/NotoSansCJKsc-Regular.otf",
607 "/usr/share/fonts/noto-cjk/NotoSerifCJK-Regular
[all...] |
| /linux/fs/cramfs/ |
| H A 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/Documentation/arch/x86/ |
| H A D | sgx.rst | 20 at a time. While the enclave is loaded from a regular binary file by using
39 Unlike pages used for regular memory, pages can only be accessed from outside of
55 **Regular (REG)**
56 Regular EPC pages contain the code and data of an enclave.
110 regular page will be dynamically added to the enclave. The enclave is
|
| /linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
| H A D | uncore-cache.json | 761 "PublicDescription": "Number of times a snoop (probe) request had to retry. Filters exist to cover some of the common cases retries.; Counts the number of times that a request form the IPQ was retried because of a TOR reject from the Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL egress to forward data, and the AK egress to return credits.",
2677 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 0",
2682 "PublicDescription": "Counts the number of cycles when there are no regular credits available for posting reads from the HA into the iMC. In order to send reads into the memory controller, the HA must first acquire a credit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers that are used by general reads, and special requests such as ISOCH reads. This count only tracks the regular credits Common high bandwidth workloads should be able to make use of all of the regular buffers, but it will be difficult (and uncommon) to make use of both the regular and special buffers at the same time. One can filter based on the memory controller channel. One or more channels can be tracked at a given time.; Filter for memory controller channel 0 only.",
2687 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 1",
2692 "PublicDescription": "Counts the number of cycles when there are no regular credits available for posting reads from the HA into the iMC. In order to send reads into the memory controller, the HA must first acquire a credit for the iMC's RPQ (read pending queue). This queue is broken into regular credit
[all...] |
| /linux/tools/perf/pmu-events/arch/x86/haswellx/ |
| H A D | uncore-cache.json | 965 "PublicDescription": "Number of times a snoop (probe) request had to retry. Filters exist to cover some of the common cases retries.; Counts the number of times that a request form the IPQ was retried because of a TOR reject from the Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL egress to forward data, and the AK egress to return credits.",
2872 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 0",
2877 "PublicDescription": "Counts the number of cycles when there are no regular credits available for posting reads from the HA into the iMC. In order to send reads into the memory controller, the HA must first acquire a credit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers that are used by general reads, and special requests such as ISOCH reads. This count only tracks the regular credits Common high bandwidth workloads should be able to make use of all of the regular buffers, but it will be difficult (and uncommon) to make use of both the regular and special buffers at the same time. One can filter based on the memory controller channel. One or more channels can be tracked at a given time.; Filter for memory controller channel 0 only.",
2882 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 1",
2887 "PublicDescription": "Counts the number of cycles when there are no regular credits available for posting reads from the HA into the iMC. In order to send reads into the memory controller, the HA must first acquire a credit for the iMC's RPQ (read pending queue). This queue is broken into regular credit
[all...] |
| /linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
| H A D | uncore-cache.json | 955 "PublicDescription": "Number of times a snoop (probe) request had to retry. Filters exist to cover some of the common cases retries.; Counts the number of times that a request form the IPQ was retried because of a TOR reject from the Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL egress to forward data, and the AK egress to return credits.",
2882 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 0",
2887 "PublicDescription": "Counts the number of cycles when there are no regular credits available for posting reads from the HA into the iMC. In order to send reads into the memory controller, the HA must first acquire a credit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers that are used by general reads, and special requests such as ISOCH reads. This count only tracks the regular credits Common high bandwidth workloads should be able to make use of all of the regular buffers, but it will be difficult (and uncommon) to make use of both the regular and special buffers at the same time. One can filter based on the memory controller channel. One or more channels can be tracked at a given time.; Filter for memory controller channel 0 only.",
2892 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 1",
2897 "PublicDescription": "Counts the number of cycles when there are no regular credits available for posting reads from the HA into the iMC. In order to send reads into the memory controller, the HA must first acquire a credit for the iMC's RPQ (read pending queue). This queue is broken into regular credit
[all...] |