| /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/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/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/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/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/kbuild/ |
| H A D | reproducible-builds.rst | 78 generate a different temporary key for each build, resulting in the
114 vDSO's debug information may be identical even for different kernel
116 packages for the different kernel versions.
118 To avoid this, you can make the vDSO different for different
125 Uncommitted changes or different commit ids in git can also lead
126 to different compilation results. For example, after executing
129 will be different, which will eventually lead to binary differences.
|
| /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/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
|
| /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/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 20 the human eye has color receptors that are sensitive to three different
23 different wavelengths, so instead of RGB we would be using the
34 possible that different SPDs will result in the same stimulation of
36 of the light is different.
68 different wavelengths, the combination of which will stimulate the color
74 Different display devices will have different primaries and some
77 different display technologies or uses. To define a colorspace you need
150 mix of different standards also led to very confusing naming conventions
|
| H A D | format.rst | 13 Different devices exchange different kinds of data with applications,
15 within one kind many different formats are possible, in particular there is an
44 example, when the new standard uses a different number of scan lines,
47 multiple file descriptors which grabbed different logical streams
|
| /linux/Documentation/virt/ |
| H A D | paravirt_ops.rst | 7 Linux provides support for different hypervisor virtualization technologies.
8 Historically, different binary kernels would be required in order to support
9 different hypervisors; this restriction was removed with pv_ops.
10 Linux pv_ops is a virtualization API which enables support for different
|
| /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/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | nvm-reg.h | 312 * The new MCC may be different than what was requested in MCC_UPDATE_CMD.
339 * The new MCC may be different than what was requested in MCC_UPDATE_CMD.
368 * The new MCC may be different than what was requested in MCC_UPDATE_CMD.
512 * different predefined FW config operation
521 * different predefined FW config operation
532 * different predefined FW config operation
547 * different predefined FW config operation.
566 * different predefined FW config operation.
589 * different predefined FW config operation.
616 * different predefined FW config operation.
[all …]
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | rt5663.txt | 23 Based on the different PCB layout, add the manual offset value to
24 compensate the DC offset for each L and R channel, and they are different
38 should compensate different DC offset to avoid the pop sound, and it is
39 also different between headphone and headset. In the example, the
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | mediatek,mt8186-pinctrl.yaml | 35 Physical address base for GPIO base registers. There are 8 different GPIO
65 define or si unit value(ohm) to set different resistance.
103 Supported pin number and mux varies for different SoCs, and are
125 set different resistance. It can support "MTK_PUPD_SET_R1R0_00" &
129 value(ohm) to set different resistance by identifying property
170 set different resistance. It can support "MTK_PUPD_SET_R1R0_00" &
174 value(ohm) to set different resistance by identifying property
|
| /linux/tools/perf/pmu-events/arch/powerpc/power8/ |
| H A D | cache.json | 5 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
6 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
11 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
12 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
17 …": "The processor's data cache was reloaded from another chip's L4 on a different Node or Group (D…
18 …": "The processor's data cache was reloaded from another chip's L4 on a different Node or Group (D…
107 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
108 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
|
| /linux/tools/testing/ktest/examples/ |
| H A D | test.conf | 8 # BOX can be different than foo, if the machine BOX has
9 # multiple partitions with different systems installed. For example,
12 # machine, which may be different between which system the machine
55 # The following files each handle a different test case.
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-health.rst | 22 generic ``devlink`` instance and allow the user to set different
38 Different parts of the driver can register different types of health reporters
39 with different handlers.
70 different SKBs. In order to do this fragmentation, it uses virtual nests
72 different SKBs.
|
| /linux/Documentation/devicetree/bindings/memory-controllers/ddr/ |
| H A D | jedec,lpddr-channel.yaml | 28 The number of DQ pins in the channel. If this number is different
31 channel (with the channel's DQ pins split up between the different
32 chips, and the CA, CS, etc. pins of the different chips all shorted
57 state of the CS pins. Different ranks may have different densities and
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | concepts.rst | 23 address ranges. Besides, different CPU architectures, and even
24 different implementations of the same architecture have different views
100 Often hardware poses restrictions on how different physical memory
112 architectures define all zones, and requirements for DMA are different
113 for different platforms.
120 different access latency depending on the "distance" from the
158 different types of data. It can be kernel internal data structures,
|