/linux/io_uring/ |
H A D | opdef.c | 59 .issue = io_nop, 74 .issue = io_read, 89 .issue = io_write, 95 .issue = io_fsync, 108 .issue = io_read_fixed, 122 .issue = io_write_fixed, 129 .issue = io_poll_add, 134 .issue = io_poll_remove, 140 .issue = io_sync_file_range, 150 .issue = io_sendmsg, [all …]
|
/linux/Documentation/admin-guide/ |
H A 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/tools/perf/pmu-events/arch/x86/icelake/ |
H A D | metricgroups.json | 100 "tma_issue2P": "Metrics related by the issue $issue2P", 101 "tma_issueBM": "Metrics related by the issue $issueBM", 102 "tma_issueBW": "Metrics related by the issue $issueBW", 103 "tma_issueComp": "Metrics related by the issue $issueComp", 104 "tma_issueD0": "Metrics related by the issue $issueD0", 105 "tma_issueFB": "Metrics related by the issue $issueFB", 106 "tma_issueFL": "Metrics related by the issue $issueFL", 107 "tma_issueL1": "Metrics related by the issue $issueL1", 108 "tma_issueLat": "Metrics related by the issue $issueLat", 109 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/skylakex/ |
H A D | metricgroups.json | 100 "tma_issue2P": "Metrics related by the issue $issue2P", 101 "tma_issueBM": "Metrics related by the issue $issueBM", 102 "tma_issueBW": "Metrics related by the issue $issueBW", 103 "tma_issueComp": "Metrics related by the issue $issueComp", 104 "tma_issueD0": "Metrics related by the issue $issueD0", 105 "tma_issueFB": "Metrics related by the issue $issueFB", 106 "tma_issueFL": "Metrics related by the issue $issueFL", 107 "tma_issueL1": "Metrics related by the issue $issueL1", 108 "tma_issueLat": "Metrics related by the issue $issueLat", 109 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
H A D | metricgroups.json | 100 "tma_issue2P": "Metrics related by the issue $issue2P", 101 "tma_issueBM": "Metrics related by the issue $issueBM", 102 "tma_issueBW": "Metrics related by the issue $issueBW", 103 "tma_issueComp": "Metrics related by the issue $issueComp", 104 "tma_issueD0": "Metrics related by the issue $issueD0", 105 "tma_issueFB": "Metrics related by the issue $issueFB", 106 "tma_issueFL": "Metrics related by the issue $issueFL", 107 "tma_issueL1": "Metrics related by the issue $issueL1", 108 "tma_issueLat": "Metrics related by the issue $issueLat", 109 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
H A D | metricgroups.json | 100 "tma_issue2P": "Metrics related by the issue $issue2P", 101 "tma_issueBM": "Metrics related by the issue $issueBM", 102 "tma_issueBW": "Metrics related by the issue $issueBW", 103 "tma_issueComp": "Metrics related by the issue $issueComp", 104 "tma_issueD0": "Metrics related by the issue $issueD0", 105 "tma_issueFB": "Metrics related by the issue $issueFB", 106 "tma_issueFL": "Metrics related by the issue $issueFL", 107 "tma_issueL1": "Metrics related by the issue $issueL1", 108 "tma_issueLat": "Metrics related by the issue $issueLat", 109 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/icelakex/ |
H A D | metricgroups.json | 101 "tma_issue2P": "Metrics related by the issue $issue2P", 102 "tma_issueBM": "Metrics related by the issue $issueBM", 103 "tma_issueBW": "Metrics related by the issue $issueBW", 104 "tma_issueComp": "Metrics related by the issue $issueComp", 105 "tma_issueD0": "Metrics related by the issue $issueD0", 106 "tma_issueFB": "Metrics related by the issue $issueFB", 107 "tma_issueFL": "Metrics related by the issue $issueFL", 108 "tma_issueL1": "Metrics related by the issue $issueL1", 109 "tma_issueLat": "Metrics related by the issue $issueLat", 110 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/skylake/ |
H A D | metricgroups.json | 99 "tma_issue2P": "Metrics related by the issue $issue2P", 100 "tma_issueBM": "Metrics related by the issue $issueBM", 101 "tma_issueBW": "Metrics related by the issue $issueBW", 102 "tma_issueComp": "Metrics related by the issue $issueComp", 103 "tma_issueD0": "Metrics related by the issue $issueD0", 104 "tma_issueFB": "Metrics related by the issue $issueFB", 105 "tma_issueFL": "Metrics related by the issue $issueFL", 106 "tma_issueL1": "Metrics related by the issue $issueL1", 107 "tma_issueLat": "Metrics related by the issue $issueLat", 108 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
H A D | metricgroups.json | 100 "tma_issue2P": "Metrics related by the issue $issue2P", 101 "tma_issueBM": "Metrics related by the issue $issueBM", 102 "tma_issueBW": "Metrics related by the issue $issueBW", 103 "tma_issueComp": "Metrics related by the issue $issueComp", 104 "tma_issueD0": "Metrics related by the issue $issueD0", 105 "tma_issueFB": "Metrics related by the issue $issueFB", 106 "tma_issueFL": "Metrics related by the issue $issueFL", 107 "tma_issueL1": "Metrics related by the issue $issueL1", 108 "tma_issueLat": "Metrics related by the issue $issueLat", 109 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
H A D | metricgroups.json | 104 "tma_issue2P": "Metrics related by the issue $issue2P", 105 "tma_issueBM": "Metrics related by the issue $issueBM", 106 "tma_issueBW": "Metrics related by the issue $issueBW", 107 "tma_issueComp": "Metrics related by the issue $issueComp", 108 "tma_issueD0": "Metrics related by the issue $issueD0", 109 "tma_issueFB": "Metrics related by the issue $issueFB", 110 "tma_issueFL": "Metrics related by the issue $issueFL", 111 "tma_issueL1": "Metrics related by the issue $issueL1", 112 "tma_issueLat": "Metrics related by the issue $issueLat", 113 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
H A D | metricgroups.json | 104 "tma_issue2P": "Metrics related by the issue $issue2P", 105 "tma_issueBM": "Metrics related by the issue $issueBM", 106 "tma_issueBW": "Metrics related by the issue $issueBW", 107 "tma_issueComp": "Metrics related by the issue $issueComp", 108 "tma_issueD0": "Metrics related by the issue $issueD0", 109 "tma_issueFB": "Metrics related by the issue $issueFB", 110 "tma_issueFL": "Metrics related by the issue $issueFL", 111 "tma_issueL1": "Metrics related by the issue $issueL1", 112 "tma_issueLat": "Metrics related by the issue $issueLat", 113 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/alderlake/ |
H A D | metricgroups.json | 109 "tma_issue2P": "Metrics related by the issue $issue2P", 110 "tma_issueBM": "Metrics related by the issue $issueBM", 111 "tma_issueBW": "Metrics related by the issue $issueBW", 112 "tma_issueComp": "Metrics related by the issue $issueComp", 113 "tma_issueD0": "Metrics related by the issue $issueD0", 114 "tma_issueFB": "Metrics related by the issue $issueFB", 115 "tma_issueFL": "Metrics related by the issue $issueFL", 116 "tma_issueL1": "Metrics related by the issue $issueL1", 117 "tma_issueLat": "Metrics related by the issue $issueLat", 118 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
H A D | metricgroups.json | 109 "tma_issue2P": "Metrics related by the issue $issue2P", 110 "tma_issueBM": "Metrics related by the issue $issueBM", 111 "tma_issueBW": "Metrics related by the issue $issueBW", 112 "tma_issueComp": "Metrics related by the issue $issueComp", 113 "tma_issueD0": "Metrics related by the issue $issueD0", 114 "tma_issueFB": "Metrics related by the issue $issueFB", 115 "tma_issueFL": "Metrics related by the issue $issueFL", 116 "tma_issueL1": "Metrics related by the issue $issueL1", 117 "tma_issueLat": "Metrics related by the issue $issueLat", 118 "tma_issueMC": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
H A D | metricgroups.json | 94 "tma_issue2P": "Metrics related by the issue $issue2P", 95 "tma_issueBM": "Metrics related by the issue $issueBM", 96 "tma_issueBW": "Metrics related by the issue $issueBW", 97 "tma_issueFB": "Metrics related by the issue $issueFB", 98 "tma_issueL1": "Metrics related by the issue $issueL1", 99 "tma_issueLat": "Metrics related by the issue $issueLat", 100 "tma_issueMC": "Metrics related by the issue $issueMC", 101 "tma_issueMS": "Metrics related by the issue $issueMS", 102 "tma_issueMV": "Metrics related by the issue $issueMV", 103 "tma_issueRFO": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
H A D | metricgroups.json | 94 "tma_issue2P": "Metrics related by the issue $issue2P", 95 "tma_issueBM": "Metrics related by the issue $issueBM", 96 "tma_issueBW": "Metrics related by the issue $issueBW", 97 "tma_issueFB": "Metrics related by the issue $issueFB", 98 "tma_issueL1": "Metrics related by the issue $issueL1", 99 "tma_issueLat": "Metrics related by the issue $issueLat", 100 "tma_issueMC": "Metrics related by the issue $issueMC", 101 "tma_issueMS": "Metrics related by the issue $issueMS", 102 "tma_issueMV": "Metrics related by the issue $issueMV", 103 "tma_issueRFO": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
H A D | metricgroups.json | 94 "tma_issue2P": "Metrics related by the issue $issue2P", 95 "tma_issueBM": "Metrics related by the issue $issueBM", 96 "tma_issueBW": "Metrics related by the issue $issueBW", 97 "tma_issueFB": "Metrics related by the issue $issueFB", 98 "tma_issueL1": "Metrics related by the issue $issueL1", 99 "tma_issueLat": "Metrics related by the issue $issueLat", 100 "tma_issueMC": "Metrics related by the issue $issueMC", 101 "tma_issueMS": "Metrics related by the issue $issueMS", 102 "tma_issueMV": "Metrics related by the issue $issueMV", 103 "tma_issueRFO": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/haswell/ |
H A D | metricgroups.json | 94 "tma_issue2P": "Metrics related by the issue $issue2P", 95 "tma_issueBM": "Metrics related by the issue $issueBM", 96 "tma_issueBW": "Metrics related by the issue $issueBW", 97 "tma_issueFB": "Metrics related by the issue $issueFB", 98 "tma_issueL1": "Metrics related by the issue $issueL1", 99 "tma_issueLat": "Metrics related by the issue $issueLat", 100 "tma_issueMC": "Metrics related by the issue $issueMC", 101 "tma_issueMS": "Metrics related by the issue $issueMS", 102 "tma_issueMV": "Metrics related by the issue $issueMV", 103 "tma_issueRFO": "Metrics related by the issue [all...] |
/linux/tools/perf/pmu-events/arch/x86/broadwell/ |
H A D | metricgroups.json | 94 "tma_issue2P": "Metrics related by the issue $issue2P", 95 "tma_issueBM": "Metrics related by the issue $issueBM", 96 "tma_issueBW": "Metrics related by the issue $issueBW", 97 "tma_issueFB": "Metrics related by the issue $issueFB", 98 "tma_issueL1": "Metrics related by the issue $issueL1", 99 "tma_issueLat": "Metrics related by the issue $issueLat", 100 "tma_issueMC": "Metrics related by the issue $issueMC", 101 "tma_issueMS": "Metrics related by the issue $issueMS", 102 "tma_issueMV": "Metrics related by the issue $issueMV", 103 "tma_issueRFO": "Metrics related by the issue [all...] |
/linux/arch/arm64/boot/dts/rockchip/ |
H A D | rk3588-jaguar-pre-ict-tester.dtso | 79 * but GPIO3_C6 would catch this HW soldering issue. 83 * issue. Therefore, let's enforce a pull-up (which is 92 * the loop doesn't exist on HW (soldering issue on 101 * but GPIO3_C6 would catch this HW soldering issue. 103 * LOW. This is an issue if GPIO3_B2 isn't properly 104 * routed due to soldering issue, because GPIO3_B2 108 * soldering issue on GPIO3_B2 reports HIGH but proper 115 * This is an issue if GPIO3_C6 or VCC_1V8_S0_1 isn't 116 * properly routed due to soldering issue, because 124 * Make GPIO3_C6 a pull-down so that a soldering issue [all …]
|
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a75/ |
H A 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/tools/perf/pmu-events/arch/arm64/ampere/emag/ |
H A 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/Documentation/kbuild/ |
H A 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"
|
H A D | issues.rst | 5 issue #1 8 .. literalinclude:: Kconfig.recursion-issue-01 11 issue #2 14 .. literalinclude:: Kconfig.recursion-issue-02
|
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a73/ |
H A 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/drivers/net/mdio/ |
H A D | mdio-ipq4019.c | 84 /* issue the phy address and mmd */ in ipq4019_mdio_read_c45() 87 /* issue reg */ in ipq4019_mdio_read_c45() 92 /* issue read command */ in ipq4019_mdio_read_c45() 125 /* issue the phy address and reg */ in ipq4019_mdio_read_c22() 130 /* issue read command */ in ipq4019_mdio_read_c22() 157 /* issue the phy address and mmd */ in ipq4019_mdio_write_c45() 160 /* issue reg */ in ipq4019_mdio_write_c45() 170 /* issue write data */ in ipq4019_mdio_write_c45() 200 /* issue the phy address and reg */ in ipq4019_mdio_write_c22() 203 /* issue write data */ in ipq4019_mdio_write_c22() [all …]
|