| /Linux-v6.1/io_uring/ |
| D | opdef.c | 55 .issue = io_nop,
69 .issue = io_read,
86 .issue = io_write,
96 .issue = io_fsync,
109 .issue = io_read,
124 .issue = io_write,
133 .issue = io_poll_add,
139 .issue = io_poll_remove,
146 .issue = io_sync_file_range,
158 .issue = io_sendmsg,
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | reporting-issues.rst | 16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
22 issue. Check the :ref:`MAINTAINERS <maintainers>` file for how its developers
27 <https://kernel.org/>`_. If the issue is present there, send a report.
29 The issue was fixed there, but you would like to see it resolved in a still
38 before the issue occurs.
42 issue, like the kernel and the distro used. In case of a regression, CC the
64 early if an issue that looks like a Linux kernel problem is actually caused by
68 * Are you facing an issue with a Linux kernel a hardware or software vendor
70 document and reporting the issue to your vendor instead, unless you are
79 * See if the issue you are dealing with qualifies as regression, security
[all …]
|
| /Linux-v6.1/tools/testing/selftests/x86/ |
| D | syscall_nt.c | 56 printf("[RUN]\tSet NT and issue a syscall\n"); in main()
59 printf("[RUN]\tSet AC and issue a syscall\n"); in main()
62 printf("[RUN]\tSet NT|AC and issue a syscall\n"); in main()
72 printf("[RUN]\tSet TF and issue a syscall\n"); in main()
75 printf("[RUN]\tSet NT|TF and issue a syscall\n"); in main()
78 printf("[RUN]\tSet AC|TF and issue a syscall\n"); in main()
81 printf("[RUN]\tSet NT|AC|TF and issue a syscall\n"); in main()
89 printf("[RUN]\tSet DF and issue a syscall\n"); in main()
92 printf("[RUN]\tSet TF|DF and issue a syscall\n"); in main()
|
| /Linux-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a75/ |
| D | pipeline.json | 27 …"PublicDescription": "Duration for which all slots in the load-store issue queue are busy. This ev…
30 …"BriefDescription": "Duration for which all slots in the load-store issue queue are busy. This eve…
33 …"PublicDescription": "Duration for which all slots in the data processing issue queue are busy. Th…
36 …"BriefDescription": "Duration for which all slots in the data processing issue queue are busy. Thi…
39 …issue queue are busy. This event is set every time that the data engine rename has at least one va…
42 …issue queue are busy. This event is set every time that the data engine rename has at least one va…
|
| /Linux-v6.1/tools/perf/pmu-events/arch/arm64/ampere/emag/ |
| D | pipeline.json | 15 "PublicDescription": "IXA Op non-issue",
21 "PublicDescription": "IXB Op non-issue",
27 "PublicDescription": "BX Op non-issue",
33 "PublicDescription": "LX Op non-issue",
39 "PublicDescription": "SX Op non-issue",
45 "PublicDescription": "FX Op non-issue",
|
| /Linux-v6.1/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 1 # Simple Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
36 # Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
41 # implications of this recursive issue where the solution is perhaps not so
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
|
| D | issues.rst | 5 issue #1
8 .. literalinclude:: Kconfig.recursion-issue-01
11 issue #2
14 .. literalinclude:: Kconfig.recursion-issue-02
|
| D | Kconfig.recursion-issue-02 | 1 # Cumulative Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
30 # other bells in the system cannot negate. The reason for this issue is
41 # For an example real world scenario issue refer to the attempt to remove
|
| D | Kconfig.select-break | 1 # Select broken dependency issue
13 # example of this issue is below.
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
|
| /Linux-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a73/ |
| D | pipeline.json | 21 "PublicDescription": "Duration for which all slots in the load-store issue queue are busy",
24 "BriefDescription": "Duration for which all slots in the load-store issue queue are busy"
27 … "PublicDescription": "Duration for which all slots in the data processing issue queue are busy",
30 … "BriefDescription": "Duration for which all slots in the data processing issue queue are busy"
33 "PublicDescription": "Duration for which all slots in the Data Engine issue queue are busy",
36 "BriefDescription": "Duration for which all slots in the Data Engine issue queue are busy"
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/snowridgex/ |
| D | pipeline.json | 366 …"BriefDescription": "Counts the total number of issue slots that were not consumed by the backend …
373 …issue slots that were not consumed by the backend because allocation is stalled due to a mispredic…
378 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
389 …"BriefDescription": "Counts the total number of issue slots that were not consumed by the backend …
400 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
422 …"BriefDescription": "Counts the total number of issue slots every cycle that were not consumed by …
432 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
443 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
454 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
465 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| D | pipeline.json | 366 …"BriefDescription": "Counts the total number of issue slots that were not consumed by the backend …
373 …issue slots that were not consumed by the backend because allocation is stalled due to a mispredic…
378 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
389 …"BriefDescription": "Counts the total number of issue slots that were not consumed by the backend …
400 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
422 …"BriefDescription": "Counts the total number of issue slots every cycle that were not consumed by …
432 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
443 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
454 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
465 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
[all …]
|
| /Linux-v6.1/rust/alloc/ |
| D | boxed.rs | 169 #[unstable(feature = "thin_box", issue = "92791")]
186 #[unstable(feature = "allocator_api", issue = "32838")] A: Allocator = Global,
226 #[unstable(feature = "new_uninit", issue = "63291")]
253 #[unstable(feature = "new_uninit", issue = "63291")]
282 #[unstable(feature = "allocator_api", issue = "32838")]
308 #[unstable(feature = "allocator_api", issue = "32838")]
309 // #[unstable(feature = "new_uninit", issue = "63291")]
334 #[unstable(feature = "allocator_api", issue = "32838")]
335 // #[unstable(feature = "new_uninit", issue = "63291")]
357 #[unstable(feature = "allocator_api", issue = "32838")]
[all …]
|
| /Linux-v6.1/drivers/net/mdio/ |
| D | mdio-ipq4019.c | 77 /* issue the phy address and mmd */ in ipq4019_mdio_read()
80 /* issue reg */ in ipq4019_mdio_read()
92 /* issue the phy address and reg */ in ipq4019_mdio_read()
98 /* issue read command */ in ipq4019_mdio_read()
140 /* issue the phy address and mmd */ in ipq4019_mdio_write()
143 /* issue reg */ in ipq4019_mdio_write()
160 /* issue the phy address and reg */ in ipq4019_mdio_write()
164 /* issue write data */ in ipq4019_mdio_write()
167 /* issue write command */ in ipq4019_mdio_write()
|
| /Linux-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/ |
| D | pipeline.json | 39 …ued due to the backend interlock. This event counts every cycle where the issue of an operation is…
42 …ued due to the backend interlock. This event counts every cycle where the issue of an operation is…
45 …o the backend, address interlock. This event counts every cycle where the issue of an operation is…
48 …o the backend, address interlock. This event counts every cycle where the issue of an operation is…
99 …ublicDescription": "Issue slot not issued due to interlock. For each cycle, this event counts each…
102 …BriefDescription": "Issue slot not issued due to interlock. For each cycle, this event counts each…
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-bus-usb-lvstest | 9 Write to this node to issue "Get Device Descriptor"
32 Write to this node to issue "Reset" for Link Layer Validation
39 Write to this node to issue "U3 entry" for Link Layer
46 Write to this node to issue "U3 exit" for Link Layer
58 Write to this node to issue "Warm Reset" for Link Layer Validation
|
| /Linux-v6.1/arch/powerpc/include/asm/ |
| D | fsl_lbc.h | 192 #define FIR_OP_CA 0x1 /* Issue current column address */
193 #define FIR_OP_PA 0x2 /* Issue current block+page address */
194 #define FIR_OP_UA 0x3 /* Issue user defined address */
195 #define FIR_OP_CM0 0x4 /* Issue command from FCR[CMD0] */
196 #define FIR_OP_CM1 0x5 /* Issue command from FCR[CMD1] */
197 #define FIR_OP_CM2 0x6 /* Issue command from FCR[CMD2] */
198 #define FIR_OP_CM3 0x7 /* Issue command from FCR[CMD3] */
203 #define FIR_OP_CW0 0xC /* Wait then issue FCR[CMD0] */
204 #define FIR_OP_CW1 0xD /* Wait then issue FCR[CMD1] */
|
| /Linux-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| D | pipeline.json | 27 …on issued due to the backend interlock.This event counts every cycle that issue is stalled and the…
30 …on issued due to the backend interlock.This event counts every cycle that issue is stalled and the…
33 …ued due to the backend, interlock, AGU.This event counts every cycle that issue is stalled and the…
36 …ued due to the backend, interlock, AGU.This event counts every cycle that issue is stalled and the…
39 …ued due to the backend, interlock, FPU.This event counts every cycle that issue is stalled and the…
42 …ued due to the backend, interlock, FPU.This event counts every cycle that issue is stalled and the…
|
| /Linux-v6.1/rust/alloc/collections/ |
| D | mod.rs | 74 issue = "48043"
86 issue = "48043"
101 issue = "none",
114 issue = "48043"
123 #[unstable(feature = "try_reserve_kind", reason = "new API", issue = "48043")]
|
| /Linux-v6.1/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 36 issue according to our documented process.
99 will form the initial response team for a particular issue. The initial
101 the issue in the best technical way.
105 immediate exclusion from the current issue and removal from all related
139 issue after confirming with the developers that they will adhere to this
142 issue after initial contact. The hardware security team is supporting the
152 entities who have already been, or should be, informed about the issue.
161 - If an expert which is required to handle an issue is employed by an
243 disclosure of a particular issue, unless requested by a response team or by
|
| D | handling-regressions.rst | 26 #. Make the Linux kernel regression tracking bot "regzbot" track the issue (this
32 when the issue started to happen::
44 description pointing to all places where the issue was reported, as
79 "regzbot" immediately start tracking the issue:
87 This tells regzbot the version range in which the issue started to happen;
115 * Point to all places where the issue was reported using "Link:" tags::
127 into the issue weeks, months, or years later. These tags are also crucial for
137 running into the issue; nevertheless developers need to take enough time and
159 free to delegate the work to the stable team, if the issue probably at no
176 reason -- for example, if the issue is likely to affect many users of the
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | pipeline.json | 249 "BriefDescription": "Unfilled issue slots per cycle",
254 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed by th…
258 "BriefDescription": "Unfilled issue slots per cycle to recover",
263 …issue slots per core cycle that were not consumed by the backend because allocation is stalled wai…
268 … "BriefDescription": "Unfilled issue slots per cycle because of a full resource in the backend",
273 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed becau…
347 …a previous unretired store in the pipeline whose address was not known at issue time, but is later…
376 …issue slots. A stream of INC instructions will not count as UOPS_NOT_DELIVERED, even though only …
|
| /Linux-v6.1/rust/alloc/vec/ |
| D | drain_filter.rs | 22 #[unstable(feature = "drain_filter", reason = "recently added", issue = "43244")]
28 #[unstable(feature = "allocator_api", issue = "32838")] A: Allocator = Global,
54 #[unstable(feature = "allocator_api", issue = "32838")]
61 #[unstable(feature = "drain_filter", reason = "recently added", issue = "43244")]
99 #[unstable(feature = "drain_filter", reason = "recently added", issue = "43244")]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | adl-metrics.json | 7 …ps). Ideally the Frontend can issue Machine_Width uops every cycle to the Backend. Frontend Bound …
150 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
342 …es how often CPU was stalled due to RFO store memory accesses; RFO store issue a read-for-ownersh…
346 …es how often CPU was stalled due to RFO store memory accesses; RFO store issue a read-for-ownersh…
448 …"BriefDescription": "This metric represents fraction of cycles the CPU issue-pipeline was stalled …
452 …"PublicDescription": "This metric represents fraction of cycles the CPU issue-pipeline was stalled…
861 …"BriefDescription": "Total issue-pipeline slots (per-Physical Core till ICL; per-Logical Processor…
868 … "BriefDescription": "Fraction of Physical Core issue-slots utilized by this Logical Processor",
1360 …"BriefDescription": "Counts the number of issue slots that were not consumed by the backend due t…
1368 …"BriefDescription": "Counts the number of issue slots that were not delivered by the frontend due…
[all …]
|
| /Linux-v6.1/drivers/gpu/drm/panfrost/ |
| D | panfrost_issues.h | 60 /* Occasionally the GPU will issue multiple page faults for the same
84 * (similar to issue 10817) and can use #10817 workaround */
135 /* Must issue a dummy job before starting real work to prevent hangs */
269 enum panfrost_hw_issue issue) in panfrost_has_hw_issue() argument
271 return test_bit(issue, pfdev->features.hw_issues); in panfrost_has_hw_issue()
|
