| /Linux-v6.6/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | marked.json | 5 …"BriefDescription": "Marked branch instruction completed with a target address less than current i…
11 "BriefDescription": "bru marked instr finish",
23 "BriefDescription": "Marked Branch Mispredicted",
29 "BriefDescription": "Marked Branch Taken completed",
35 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
41 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
47 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
53 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
59 …e was reloaded from another chip's L4 on a different Node or Group (Distant) due to a marked load",
65 …cles to reload from another chip's L4 on a different Node or Group (Distant) due to a marked load",
[all …]
|
| D | other.json | 119 "BriefDescription": "marked two path branch",
647 …"BriefDescription": "Stream marked valid. The stream could have been allocated through the hardwar…
1121 "BriefDescription": "Instruction Marked",
1122 "PublicDescription": "Instruction marked in idu"
1739 "BriefDescription": "TM marked store abort",
2502 "PublicDescription": "IFU non-branch marked instruction finished"
2507 … was reloaded with Modified (M) data from another core's L2 on the same chip due to a marked load",
2513 …les to reload with Modified (M) data from another core's L2 on the same chip due to a marked load",
2519 …he was reloaded with Shared (S) data from another core's L2 on the same chip due to a marked load",
2525 …ycles to reload with Shared (S) data from another core's L2 on the same chip due to a marked load",
[all …]
|
| D | metrics.json | 1344 "BriefDescription": "average L1 miss latency using marked events",
1392 "BriefDescription": "Marked background kill latency, measured in L2",
1398 "BriefDescription": "Marked dclaim latency, measured in L2",
1404 "BriefDescription": "Marked L2L3 remote Load latency",
1410 "BriefDescription": "Marked L2L3 distant Load latency",
1422 "BriefDescription": "Marked Dmem Load latency",
1434 …"BriefDescription": "Average load latency for all marked demand loads that came from L2.1 in the M…
1440 …"BriefDescription": "Average load latency for all marked demand loads that came from L2.1 in the S…
1446 …"BriefDescription": "Average load latency for all marked demand loads that came from the L2 and su…
1452 …"BriefDescription": "Average load latency for all marked demand loads that came from the L2 and su…
[all …]
|
| /Linux-v6.6/tools/perf/pmu-events/arch/powerpc/power10/ |
| D | marked.json | 5 …"BriefDescription": "Marked instruction issued. Note that stores always get issued twice, the addr…
10 "BriefDescription": "Marked store completed in L2."
15 …"BriefDescription": "For a marked data transfer instruction, the processor's L1 data cache was rel…
20 …"BriefDescription": "Cycles taken for a marked demand miss to reload a line from the source specif…
25 …"BriefDescription": "Marked Data TLB reload (after a miss) page size 1G. Implies radix translation…
35 "BriefDescription": "The thread has dispatched a randomly sampled marked instruction."
40 "BriefDescription": "Marked Branch Taken instruction completed."
45 "BriefDescription": "Marked instruction suffered an instruction cache miss."
50 "BriefDescription": "Marked demand reload."
55 "BriefDescription": "Marked instruction RC dispatched in L2."
[all …]
|
| /Linux-v6.6/tools/memory-model/ |
| D | linux-kernel.cat | 84 let to-r = (addr ; [R]) | (dep ; [Marked] ; rfi)
88 let A-cumul(r) = (rfe ; [Marked])? ; r
90 let cumul-fence = [Marked] ; (A-cumul(strong-fence | po-rel) | wmb |
91 po-unlock-lock-po) ; [Marked] ; rmw-sequence
92 let prop = [Marked] ; (overwrite & ext)? ; cumul-fence* ;
93 [Marked] ; rfe? ; [Marked]
99 let hb = [Marked] ; (ppo | rfe | ((prop \ id) & int)) ; [Marked]
107 let pb = prop ; strong-fence ; hb* ; [Marked]
159 let rb = prop ; rcu-fence ; hb* ; pb* ; [Marked]
176 (* Warn about plain writes and marked accesses in the same region *)
[all …]
|
| /Linux-v6.6/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | pipeline.json | 15 …"BriefDescription": "Marked DL1 Demand Miss counted at exec time. Note that this count is per slic…
30 …ded either shared or modified data from another core's L2/L3 on the same chip due to a marked load"
35 …B from another chip's L4 on a different Node or Group (Distant) due to a marked data side request.…
80 … with Modified (M) data from another core's L2 on the same chip due to a marked data side request.…
105 "BriefDescription": "Marked fixed point divide that can cause a synchronous interrupt"
115 …m local core's L3 without dispatch conflicts hit on Mepf state. due to a marked data side request.…
120 …"BriefDescription": "Marked Data ERAT Miss (Data TLB Access) page size 16G (hpt mode) and 1G (radi…
160 …om another core's L2/L3 on a different chip (remote or distant) due to a marked data side request.…
180 …y was loaded into the TLB from local core's L2 without conflict due to a marked data side request.…
190 …from another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked load"
[all …]
|
| D | marked.json | 5 …"BriefDescription": "Number of cycles the marked instruction is experiencing a stall while it is n…
15 …"BriefDescription": "An instruction was marked. Includes both Random Instruction Sampling (RIS) at…
60 …le Entry was loaded into the TLB from the local chip's L4 cache due to a marked data side request.…
65 …"BriefDescription": "An instruction was marked at decode time. Random Instruction Sampling (RIS) o…
70 …ith Shared (S) data from another core's ECO L3 on the same chip due to a marked data side request.…
95 …h Modified (M) data from another core's ECO L3 on the same chip due to a marked data side request.…
110 … "Duration in cycles to reload from a location other than the local core's L3 due to a marked load"
175 "BriefDescription": "Marked instruction issued"
210 …able Entry was loaded into the TLB from the local chip's Memory due to a marked data side request.…
220 …ded into the TLB from a location other than the local core's L3 due to a marked data side request.…
[all …]
|
| D | frontend.json | 45 "BriefDescription": "Marked Instruction RC dispatched in L2"
65 "BriefDescription": "Marked store had to do a dclaim"
150 …ocessor's data cache was reloaded from local core's L2 with dispatch conflict due to a marked load"
155 …from another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked load"
170 …oad either shared or modified data from another core's L2/L3 on the same chip due to a marked load"
235 "BriefDescription": "Marked Branch mispredict that can cause a synchronous interrupt"
240 "BriefDescription": "Marked instruction was reloaded from a location beyond the local chiplet"
250 "BriefDescription": "Marked Branch and link branch that can cause a synchronous interrupt"
260 "BriefDescription": "Marked Load exposed Miss (use edge detect to count #)"
330 …cache was reloaded from another chip's L4 on the same Node or Group ( Remote) due to a marked load"
[all …]
|
| D | other.json | 45 …ssor's data cache was reloaded from a location other than the local core's L3 due to a marked load"
205 … to reload with Modified (M) data from another core's ECO L3 on the same chip due to a marked load"
225 …cles to reload from another chip's memory on the same Node or Group (Distant) due to a marked load"
230 "BriefDescription": "Duration in cycles to reload from local core's L2 due to a marked load"
255 …r's data cache was reloaded from local core's L2 with load hit store conflict due to a marked load"
290 "BriefDescription": "Marked instruction was reloaded from a location beyond the local chiplet"
320 …e was reloaded from another chip's memory on the same Node or Group ( Remote) due to a marked load"
350 …s to reload from local core's L3 without dispatch conflicts hit on Mepf state due to a marked load"
365 "BriefDescription": "Marked demand reload"
370 "BriefDescription": "Marked ld latency"
[all …]
|
| D | pmc.json | 20 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data side request.…
40 …ded into the TLB from a location other than the local core's L2 due to a marked data side request.…
55 …ption": "The processor's data cache was reloaded from the local chip's Memory due to a marked load"
70 …"BriefDescription": "Duration in cycles to reload from the local chip's Memory due to a marked loa…
95 …loaded into the TLB from local core's L3 with dispatch conflict due to a marked data side request.…
100 …A Page Table Entry was loaded into the TLB from local core's L3 due to a marked data side request.…
|
| D | translation.json | 40 "BriefDescription": "lsu marked instr PPC finish"
55 …cription": "Cycles during which the marked instruction is next to complete (completion is held up …
135 …from another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked load"
190 "BriefDescription": "Marked probeNops completed"
200 …es to reload with Shared (S) data from another core's ECO L3 on the same chip due to a marked load"
|
| D | cache.json | 25 …n cycles to reload from another chip's L4 on the same Node or Group ( Remote) due to a marked load"
70 …m local core's L2 hit without dispatch conflicts on Mepf state. due to a marked data side request.…
80 … from another chip's memory on the same Node or Group ( Remote) due to a marked data side request.…
95 "BriefDescription": "Marked dtlb miss"
|
| /Linux-v6.6/tools/testing/selftests/drivers/net/mlxsw/ |
| D | rtnetlink.sh | 510 # marked as offloaded
520 check_err $? "fdb entry not marked as offloaded when should"
529 # Test that IPv4 and IPv6 neighbour entries are marked as offloaded
541 check_err $? "ipv4 neigh entry not marked as offloaded when should"
544 check_err $? "ipv6 neigh entry not marked as offloaded when should"
556 # Test that IPv4 and IPv6 nexthops are marked as offloaded
571 check_err $? "ipv4 nexthop not marked as offloaded when should"
574 check_err $? "ipv6 nexthop not marked as offloaded when should"
581 check_err $? "ipv4 nexthop marked as offloaded when should not"
584 check_err $? "ipv6 nexthop marked as offloaded when should not"
[all …]
|
| /Linux-v6.6/Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7606.yaml | 44 input channels. As the line is active high, it should be marked
52 it should be marked GPIO_ACTIVE_HIGH.
59 Shutdown mode. As the line is active low, it should be marked
68 As the line is active high, it should be marked GPIO_ACTIVE_HIGH.
77 is ±5V for all channels. As the line is active high, it should be marked
84 mode pins. As the line is active high, it should be marked
|
| D | adi,ad7780.yaml | 47 line is active high, it should be marked GPIO_ACTIVE_HIGH.
54 driver probe. As the line is active low, it should be marked
63 marked GPIO_ACTIVE_LOW.
|
| /Linux-v6.6/fs/btrfs/tests/ |
| D | free-space-tests.c | 415 * with existing extent entries - the space ends up being marked in test_steal_space_from_bitmap_to_extent()
451 * Now make only the first 256Kb of the bitmap marked as free, so that in test_steal_space_from_bitmap_to_extent()
452 * we end up with only the following ranges marked as free space: in test_steal_space_from_bitmap_to_extent()
465 /* Confirm that only those 2 ranges are marked as free. */ in test_steal_space_from_bitmap_to_extent()
476 * Confirm that the bitmap range [128Mb + 768Kb, 256Mb[ isn't marked in test_steal_space_from_bitmap_to_extent()
487 * covered by the bitmap, isn't marked as free. in test_steal_space_from_bitmap_to_extent()
490 test_err("invalid bitmap region marked as free"); in test_steal_space_from_bitmap_to_extent()
496 * by the bitmap too, isn't marked as free either. in test_steal_space_from_bitmap_to_extent()
499 test_err("invalid bitmap region marked as free"); in test_steal_space_from_bitmap_to_extent()
513 /* Confirm the region is marked as free. */ in test_steal_space_from_bitmap_to_extent()
[all …]
|
| /Linux-v6.6/arch/powerpc/perf/ |
| D | power8-events-list.h | 56 /* Marked store completed */
58 /* Alternate event code for Marked store completed */
60 /* Marked two path branch */
68 /* Data cache was reloaded from a location other than L2 due to a marked load */
82 /* Marked filter Match */
|
| /Linux-v6.6/lib/ |
| D | Kconfig.kcsan | 224 writes up to word size: conflicts between marked reads and plain
230 bool "Do not instrument marked atomic accesses"
233 Never instrument marked atomic accesses. This option can be used for
234 additional filtering. Conflicting marked atomic reads and plain
236 plain reads and marked writes to result in "unknown origin" reports.
238 races where at least one access is marked atomic will never be
242 accesses, conflicting marked atomic reads and plain writes will not
|
| /Linux-v6.6/tools/include/uapi/linux/ |
| D | pkt_sched.h | 223 __u32 prob_mark; /* Marked packets, below max threshold */
224 __u32 forced_mark; /* Marked packets, after max threshold */
225 __u32 prob_mark_head; /* Marked packets, below max threshold */
226 __u32 forced_mark_head;/* Marked packets, after max threshold */
280 __u32 marked; /* Marked packets */ member
380 __u32 marked; /* Marked packets */ member
757 __u32 marked; member
803 __u32 ecn_mark; /* number of packets we ECN marked instead of dropped */
805 __u32 ce_mark; /* number of CE marked packets because of ce_threshold */
836 __u32 ecn_mark; /* number of packets we ECN marked
[all …]
|
| /Linux-v6.6/include/uapi/linux/ |
| D | pkt_sched.h | 224 __u32 prob_mark; /* Marked packets, below max threshold */
225 __u32 forced_mark; /* Marked packets, after max threshold */
226 __u32 prob_mark_head; /* Marked packets, below max threshold */
227 __u32 forced_mark_head;/* Marked packets, after max threshold */
300 __u32 marked; /* Marked packets */ member
400 __u32 marked; /* Marked packets */ member
794 __u32 marked; member
840 __u32 ecn_mark; /* number of packets we ECN marked instead of dropped */
842 __u32 ce_mark; /* number of CE marked packets because of ce_threshold */
877 __u32 ecn_mark; /* number of packets we ECN marked
[all …]
|
| /Linux-v6.6/drivers/hwtracing/coresight/ |
| D | coresight-trace-id.h | 53 * Initialised so that the reserved IDs are permanently marked as
56 * yet marked as available, to allow re-allocation to the same
87 * If a perf session is in operation then the ID will be marked as pending
151 * if this causes the count to go to zero, then all Trace IDs marked as pending
|
| /Linux-v6.6/Documentation/dev-tools/ |
| D | kcsan.rst | 206 KCSAN is aware of *marked atomic operations* (``READ_ONCE``, ``WRITE_ONCE``,
264 To detect data races between plain and marked accesses, KCSAN also annotates
265 marked accesses, but only to check if a watchpoint exists; i.e. KCSAN never
266 sets up a watchpoint on marked accesses. By never setting up watchpoints for
267 marked operations, if all accesses to a variable that is accessed concurrently
268 are properly marked, KCSAN will never trigger a watchpoint and therefore never
314 means reordering of marked accesses is not modeled.
317 instrumentation (no prefetching). Furthermore, marked accesses introducing
318 address or control dependencies do not require special handling (the marked
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 67 2. Data-racy reads whose values are checked against marked reload.
101 Data-Racy Reads That Are Checked Against Marked Reload
104 fed into some operation that checks the full value against a later marked
211 It is important to comment marked accesses so that people reading your
222 if that concurrent access is marked with READ_ONCE(). In addition,
226 write is marked with data_race() or WRITE_ONCE().
297 this function can be marked __no_kcsan and the data_race() can be dropped:
343 Because foo is read locklessly, all accesses are marked. The purpose
464 Because foo is accessed locklessly, all accesses are marked. It does
513 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
| D | ordering.txt | 415 A control dependency extends from a marked load (READ_ONCE() or stronger)
416 through an "if" condition to a marked store (WRITE_ONCE() or stronger)
443 a. Unordered marked operations.
448 Unordered Marked Operations
454 of unordered marked accesses can also be constrained using the mechanisms
459 o Marked writes, such as WRITE_ONCE() and atomic_set(). These
464 reorder marked writes with each other or with other unordered
467 o Marked reads, such as READ_ONCE() and atomic_read(). These
472 reorder marked reads with each other or with other unordered
528 accesses is a write, whether marked or not.)
|
| /Linux-v6.6/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 30 A page is considered idle if it has not been accessed since it was marked idle
83 set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The
96 exceeding the dirty memory limit, it is not marked referenced.
104 When a page is marked idle, the Accessed bit must be cleared in all PTEs it is
|
