| /Linux-v5.4/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-v5.4/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"
|
| D | kconfig-language.rst | 542 into a recursive dependency issue with Kconfig, a recursive dependency can be
548 Kconfig recursive issue" subsection below. Kconfig does not do recursive
555 Simple Kconfig recursive issue
558 Read: Documentation/kbuild/Kconfig.recursion-issue-01
562 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
564 Cumulative Kconfig recursive issue
567 Read: Documentation/kbuild/Kconfig.recursion-issue-02
571 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
573 Practical solutions to kconfig recursive issue
576 Developers who run into the recursive Kconfig issue have two options
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | other.json | 24 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed by th…
30 "BriefDescription": "Unfilled issue slots per cycle"
34 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed becau…
40 … "BriefDescription": "Unfilled issue slots per cycle because of a full resource in the backend"
44 …issue slots per core cycle that were not consumed by the backend because allocation is stalled wai…
50 "BriefDescription": "Unfilled issue slots per cycle to recover"
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | other.json | 28 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed by th…
36 "BriefDescription": "Unfilled issue slots per cycle"
40 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed becau…
48 … "BriefDescription": "Unfilled issue slots per cycle because of a full resource in the backend"
52 …issue slots per core cycle that were not consumed by the backend because allocation is stalled wai…
60 "BriefDescription": "Unfilled issue slots per cycle to recover"
|
| /Linux-v5.4/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-v5.4/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-v5.4/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | jkt-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
96 "BriefDescription": "Total issue-pipeline slots (per core)",
102 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/sandybridge/ |
| D | snb-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
96 "BriefDescription": "Total issue-pipeline slots (per core)",
102 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/include/linux/ |
| D | blk_types.h | 98 * 51 bits: issue time of bio
121 static inline u64 bio_issue_time(struct bio_issue *issue) in bio_issue_time() argument
123 return __bio_issue_time(issue->value); in bio_issue_time()
126 static inline sector_t bio_issue_size(struct bio_issue *issue) in bio_issue_size() argument
128 return ((issue->value & BIO_ISSUE_SIZE_MASK) >> BIO_ISSUE_SIZE_SHIFT); in bio_issue_size()
131 static inline void bio_issue_init(struct bio_issue *issue, in bio_issue_init() argument
135 issue->value = ((issue->value & BIO_ISSUE_RES_MASK) | in bio_issue_init()
322 * When a shared kthread needs to issue a bio for a cgroup, doing
|
| /Linux-v5.4/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 34 issue according to our documented process.
94 will form the initial response team for a particular issue. The initial
96 the issue in the best technical way.
100 immediate exclusion from the current issue and removal from all related
134 issue after confirming with the developers that they will adhere to this
137 issue after initial contact. The hardware security team is supporting the
147 entities who have already been, or should be, informed about the issue.
156 - If an expert which is required to handle an issue is employed by an
238 disclosure of a particular issue, unless requested by a response team or by
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/haswell/ |
| D | hsw-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | hsx-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | ivt-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | ivb-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/broadwell/ |
| D | bdw-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/skylake/ |
| D | skl-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/samples/bpf/ |
| D | xdp_rxq_info_user.c | 185 __u64 issue; member
283 rec->cpu[i].issue = values[i].issue; in map_collect_percpu()
284 sum_issue += values[i].issue; in map_collect_percpu()
287 rec->total.issue = sum_issue; in map_collect_percpu()
335 packets = r->issue - p->issue; in calc_errs_pps()
364 "XDP stats", "CPU", "pps", "issue-pps"); in stats_print()
388 "RXQ stats", "RXQ:CPU", "pps", "issue-pps"); in stats_print()
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | bdx-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | clx-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | skx-metrics.json | 4 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
11 …ps (uops). Ideally the Frontend can issue 4 uops every cycle to the Backend. Frontend Bound denote…
18 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
25 …eculations. This include slots used to issue uops that do not eventually get retired and slots for…
108 "BriefDescription": "Total issue-pipeline slots (per core)",
114 "BriefDescription": "Total issue-pipeline slots (per core)",
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 25 indication of a bus allocation issue. The interrupt mechanism can also help
35 Slave or to a non-implemented register) or electrical issue, no response
39 solution. Alternatively some implementations might directly issue a bus
|
