| /linux/tools/perf/pmu-events/arch/x86/amdzen5/ |
| H A D | load-store.json | 96 …"BriefDescription": "Demand data cache fills from L3 cache or different L2 cache in the same CCX.",
102 …"BriefDescription": "Demand data cache fills from local L2 cache, L3 cache or different L2 cache i…
120 …"Demand data cache fills from cache of another CCX when the address was in a different NUMA node.",
126 … cache fills from cache of another CCX when the address was in the same or a different NUMA node.",
132 …: "Demand data cache fills from either DRAM or MMIO in a different NUMA node (same or different so…
138 …ta cache fills from either DRAM or MMIO in the same or a different NUMA node (same or different so…
144 …e of another CCX, DRAM or MMIO when the address was in a different NUMA node (same or different so…
168 "BriefDescription": "Any data cache fills from L3 cache or different L2 cache in the same CCX.",
174 …"BriefDescription": "Any data cache fills from local L2 cache or L3 cache or different L2 cache in…
192 …": "Any data cache fills from cache of another CCX when the address was in a different NUMA node.",
[all …]
|
| H A D | l3-cache.json | 37 …"BriefDescription": "Average sampled latency when data is sourced from DRAM in a different NUMA no…
59 …ency when data is sourced from another CCX's cache when the address was in a different NUMA node.",
81 …verage sampled latency when data is sourced from extension memory (CXL) in a different NUMA node.",
114 "BriefDescription": "L3 cache fill requests sourced from DRAM in a different NUMA node.",
136 …che fill requests sourced from another CCX's cache when the address was in a different NUMA node.",
158 …"BriefDescription": "L3 cache fill requests sourced from extension memory (CXL) in a different NUM…
|
| /linux/Documentation/process/ |
| H A D | stable-api-nonsense.rst | 64 - Depending on the version of the C compiler you use, different kernel
65 data structures will contain different alignment of structures, and
66 possibly include different functions in different ways (putting
68 isn't that important, but the different data structure padding is
72 different things can be assumed by the kernel:
74 - different structures can contain different fields
77 - Memory within the kernel can be aligned in different ways,
80 - Linux runs on a wide range of different processor architectures.
89 different Linux distributions and the number of different supported
91 different build options on different releases. Also realize that each
[all …]
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | spin_lock.c | 34 { "lock_id_mismatch_kptr_kptr", "bpf_spin_unlock of different lock" },
35 { "lock_id_mismatch_kptr_global", "bpf_spin_unlock of different lock" },
36 { "lock_id_mismatch_kptr_mapval", "bpf_spin_unlock of different lock" },
37 { "lock_id_mismatch_kptr_innermapval", "bpf_spin_unlock of different lock" },
38 { "lock_id_mismatch_global_global", "bpf_spin_unlock of different lock" },
39 { "lock_id_mismatch_global_kptr", "bpf_spin_unlock of different lock" },
40 { "lock_id_mismatch_global_mapval", "bpf_spin_unlock of different lock" },
41 { "lock_id_mismatch_global_innermapval", "bpf_spin_unlock of different lock" },
42 { "lock_id_mismatch_mapval_mapval", "bpf_spin_unlock of different lock" },
43 { "lock_id_mismatch_mapval_kptr", "bpf_spin_unlock of different lock" },
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen6/ |
| H A D | load-store.json | 102 …"BriefDescription": "Demand data cache fills where data is returned from L3 cache or different L2 …
108 …ata cache fills where data is returned from local L2 cache, L3 cache or different L2 cache in the …
126 …emand data cache fills where data is returned from cache of another CCX in a different NUMA node.",
132 …ache fills where data is returned from cache of another CCX in the same or a different NUMA node.",
138 …Demand data cache fills where data is returned from either DRAM or MMIO in a different NUMA node.",
144 …cache fills where data is returned from either DRAM or MMIO in the same or a different NUMA node.",
150 …s where data is returned from either cache of another CCX, DRAM or MMIO in a different NUMA node.",
174 …"BriefDescription": "Any data cache fills where data is returned from L3 cache or different L2 cac…
180 …ata cache fills where data is returned from local L2 cache, L3 cache or different L2 cache in the …
198 … "Any data cache fills where data is returned from cache of another CCX in a different NUMA node.",
[all …]
|
| H A D | inst-cache.json | 57 …"BriefDescription": "Instruction cache fills where data is returned from L3 cache or different L2 …
63 …ion cache fills where data is returned from local L2 cache, L3 cache or different L2 cache in the …
81 …nstruction cache fills where data is returned from cache of another CCX in a different NUMA node.",
87 …ache fills where data is returned from cache of another CCX in the same or a different NUMA node.",
93 …Instruction cache fills where data is returned from either DRAM or MMIO in a different NUMA node.",
99 …cache fills where data is returned from either DRAM or MMIO in the same or a different NUMA node.",
105 …s where data is returned from either cache of another CCX, DRAM or MMIO in a different NUMA node.",
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen4/ |
| H A D | cache.json | 29 …"BriefDescription": "Demand data cache fills from L3 cache or different L2 cache in the same CCX.",
47 …"Demand data cache fills from cache of another CCX when the address was in a different NUMA node.",
53 …: "Demand data cache fills from either DRAM or MMIO in a different NUMA node (same or different so…
77 "BriefDescription": "Any data cache fills from L3 cache or different L2 cache in the same CCX.",
83 …"BriefDescription": "Any data cache fills from local L2 cache or L3 cache or different L2 cache in…
101 …": "Any data cache fills from cache of another CCX when the address was in a different NUMA node.",
107 … cache fills from cache of another CCX when the address was in the same or a different NUMA node.",
113 …on": "Any data cache fills from either DRAM or MMIO in a different NUMA node (same or different so…
119 …ion": "Any data cache fills from either DRAM or MMIO in any NUMA node (same or different socket).",
125 …e of another CCX, DRAM or MMIO when the address was in a different NUMA node (same or different so…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen3/ |
| H A D | memory.json | 132 …scription": "Demand Data Cache Fills by Data Source. From DRAM or IO connected in different Node.",
138 "BriefDescription": "Demand Data Cache Fills by Data Source. From CCX Cache in different Node.",
150 …"BriefDescription": "Demand Data Cache Fills by Data Source. From cache of different CCX in same n…
156 …"BriefDescription": "Demand Data Cache Fills by Data Source. From L3 or different L2 in same CCX.",
168 …fDescription": "Any Data Cache Fills by Data Source. From DRAM or IO connected in different Node.",
174 "BriefDescription": "Any Data Cache Fills by Data Source. From CCX Cache in different Node.",
186 …"BriefDescription": "Any Data Cache Fills by Data Source. From cache of different CCX in same node…
192 "BriefDescription": "Any Data Cache Fills by Data Source. From L3 or different L2 in same CCX.",
342 … "Software Prefetch Data Cache Fills by Data Source. From DRAM or IO connected in different Node.",
348 …scription": "Software Prefetch Data Cache Fills by Data Source. From CCX Cache in different Node.",
[all …]
|
| /linux/tools/testing/selftests/net/forwarding/ |
| H A D | tc_vlan_modify.sh | 108 check_fail $? "ping between two different vlans passed when should not"
111 check_fail $? "ping6 between two different vlans passed when should not"
119 check_err $? "ping between two different vlans failed when should not"
122 check_err $? "ping6 between two different vlans failed when should not"
135 check_fail $? "ping between two different vlans passed when should not"
138 check_fail $? "ping6 between two different vlans passed when should not"
146 check_err $? "ping between two different vlans failed when should not"
149 check_err $? "ping6 between two different vlans failed when should not"
|
| /linux/tools/testing/selftests/net/ |
| H A D | bridge_vlan_dump.sh | 6 # VLANs with different per-VLAN option values are not grouped together.
43 # Configure different neigh_suppress values and verify no range grouping
52 check_fail $? "VLANs with different neigh_suppress incorrectly grouped"
81 # Configure different mcast_max_groups values and verify no range grouping
90 check_fail $? "VLANs with different mcast_max_groups incorrectly grouped"
119 # Add different numbers of multicast groups to each VLAN
132 # Verify VLANs are not shown as a range due to different mcast_n_groups
134 check_fail $? "VLANs with different mcast_n_groups incorrectly grouped"
170 # Configure different mcast_snooping for bridge VLANs
175 # Verify port VLANs are not grouped due to different mcast_enabled
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | delay.rst | 6 and/or flushes and optionally maps them to different devices.
18 to write and flush operations on optionally different write_device with
19 optionally different sector offset
22 on/with optionally different flush_device/flush_offset.
43 # splitting reads to device $1 but writes and flushes to different device $2
44 # to different offsets of 2048 and 4096 sectors respectively.
|
| /linux/Documentation/arch/powerpc/ |
| H A D | vcpudispatch_stats.rst | 11 scenarios, vcpus may be dispatched on a different processor chip (away
33 3. number of times this vcpu was dispatched on a different processor core
35 4. number of times this vcpu was dispatched on a different chip
36 5. number of times this vcpu was dispatches on a different socket/drawer
43 7. number of times this vcpu was dispatched in a different node
69 physical cpu as the last time. 2683 were on a different core, but within
70 the same chip, while 30 dispatches were on a different chip compared to
|
| /linux/include/uapi/linux/ |
| H A D | falloc.h | 20 * Different filesystems may implement different limitations on the
52 * Different filesystems may implement different limitations on the granularity
69 * Different filesystems may implement different limitations on the
89 * Different filesystems may implement different limitations on the
|
| /linux/Documentation/kbuild/ |
| H A D | reproducible-builds.rst | 81 generate a different temporary key for each build, resulting in the
117 vDSO's debug information may be identical even for different kernel
119 packages for the different kernel versions.
121 To avoid this, you can make the vDSO different for different
128 Uncommitted changes or different commit ids in git can also lead
129 to different compilation results. For example, after executing
132 will be different, which will eventually lead to binary differences.
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | samsung,s5m8767.yaml | 36 Describes the different operating modes of the LDO's with power mode
37 change in SOC. The different possible values are:
60 Describes the different operating modes of the regulator with power
61 mode change in SOC. The different possible values are:
85 Describes the different operating modes of the regulator with power
86 mode change in SOC. The different possible values are:
|
| /linux/Documentation/admin-guide/namespaces/ |
| H A D | compatibility-list.rst | 6 may have when creating tasks living in different namespaces.
10 in different other namespaces (the rows):
28 other task living in a different namespace via a shared filesystem
33 2. Intentionally, two equal user IDs in different user namespaces
40 from different user namespaces should not access the same IPC objects
|
| /linux/Documentation/admin-guide/media/ |
| H A D | rkcif.rst | 11 different variants.
12 The different variants are combinations of common building blocks, such as
14 * INTERFACE blocks of different types, namely
37 This document describes the different variants of the CIF, their hardware
62 DVP features four DMA engines that can capture different streams.
64 handle different Virtual Channels (VCs).
|
| /linux/tools/perf/pmu-events/arch/powerpc/power10/ |
| H A D | datasource.json | 350 …in the M (exclusive) state from another core's L2 on the same chip in a different regent due to a …
355 …in the M (exclusive) state from another core's L2 on the same chip in a different regent due to a …
360 …in the M (exclusive) state from another core's L2 on the same chip in a different regent due to a …
365 …in the M (exclusive) state from another core's L2 on the same chip in a different regent due to a …
370 …ruction cache was reloaded from another core's L2 on the same chip in a different regent due to a …
375 …L1 data cache was reloaded from another core's L2 on the same chip in a different regent due to a …
380 …ruction cache was reloaded from another core's L2 on the same chip in a different regent due to a …
385 …L1 data cache was reloaded from another core's L2 on the same chip in a different regent due to a …
390 …in the M (exclusive) state from another core's L3 on the same chip in a different regent due to a …
395 …in the M (exclusive) state from another core's L3 on the same chip in a different regent due to a …
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 21 the human eye has color receptors that are sensitive to three different
24 different wavelengths, so instead of RGB we would be using the
35 possible that different SPDs will result in the same stimulation of
37 of the light is different.
69 different wavelengths, the combination of which will stimulate the color
75 Different display devices will have different primaries and some
78 different display technologies or uses. To define a colorspace you need
151 mix of different standards also led to very confusing naming conventions
|
| /linux/tools/perf/pmu-events/arch/x86/sierraforest/ |
| H A D | uncore-io.json | 436 …"BriefDescription": "Data requested by the CPU : Another card (different IIO stack) reading from t…
447 …"BriefDescription": "Data requested by the CPU : Another card (different IIO stack) writing to thi…
656 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
668 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
680 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
692 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
704 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
716 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
728 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
740 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | uncore-io.json | 436 …"BriefDescription": "Data requested by the CPU : Another card (different IIO stack) reading from t…
447 …"BriefDescription": "Data requested by the CPU : Another card (different IIO stack) writing to thi…
656 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
668 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
680 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
692 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
704 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
716 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
728 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
740 …scription": "Data requested of the CPU : Card reading from another Card (same or different stack)",
[all …]
|
| /linux/drivers/gpu/drm/msm/ |
| H A D | NOTES | 3 In the current snapdragon SoC's, we have (at least) 3 different
20 with N different kms devices from xf86-video-freedreno. Plus, it
25 So, the approach is one drm driver, with some modularity. Different
27 And one or more 'struct msm_gpu' for the various different gpu sub-
57 than needing a different implementation for DTV, DSI, etc. (Ie. the
58 register interface is same, just different bases.)
|
| /linux/fs/hfs/ |
| H A D | string_test.c | 24 /* Test different lengths */ in hfs_strcmp_test()
48 char name3[] = "different"; in hfs_hash_dentry_test()
71 /* Different names should have different hashes */ in hfs_hash_dentry_test()
95 /* Test different names */ in hfs_compare_dentry_test()
99 /* Test different lengths */ in hfs_compare_dentry_test()
|
| /linux/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/ |
| H A D | l3_cache.json | 123 …2D_CACHE_REFILL_L3D_MISS_DM where the requests access the memory in the different socket from the …
128 …event counts L2D_CACHE_REFILL_L3D_MISS_DM where the requests access the different L2 cache from th…
133 … L2D_CACHE_REFILL_L3D_MISS_DM where the requests access L2 cache in the different Numa nodes from …
138 … L2D_CACHE_REFILL_L3D_MISS_DM where the requests access L3 cache in the different Numa nodes from …
143 … L2D_CACHE_REFILL_L3D_MISS_DM where the requests access L2 cache in the different socket from the …
148 … L2D_CACHE_REFILL_L3D_MISS_DM where the requests access L3 cache in the different socket from the …
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v3/ |
| H A D | tlb.json | 28 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
32 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
92 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
96 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
100 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
104 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
124 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
128 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
132 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
136 …even if the translation ended up taking a translation fault for reasons different than EPD, E0PD a…
|