| /linux/net/openvswitch/ |
| H A D | Kconfig | 28 which are often characterized by highly dynamic endpoints and the
|
| /linux/arch/arm/mach-omap2/ |
| H A D | opp2430_data.c | 11 * These configurations are characterized by voltage and speed for clocks.
|
| H A D | opp2420_data.c | 11 * These configurations are characterized by voltage and speed for clocks.
|
| H A D | opp2xxx.h | 11 * These configurations are characterized by voltage and speed for clocks.
|
| /linux/drivers/phy/broadcom/ |
| H A D | phy-brcm-sata.c | 243 /* These defaults were characterized by H/W group */
422 /* NS2 SATA PLL1 defaults were characterized by H/W group */
|
| /linux/drivers/media/i2c/ |
| H A D | max9271.c | 140 * characterized in the serializer manual. Sleep up to 5msec to in max9271_configure_i2c()
|
| /linux/drivers/iio/chemical/ |
| H A D | sunrise_co2.c | 34 * The calibration timeout is not characterized in the datasheet.
|
| /linux/Documentation/devicetree/bindings/cpu/ |
| H A D | idle-states.yaml | 45 be characterized with bindings that provide the required information to OS PM
70 Idle states are characterized for a specific system through a set of
|
| /linux/tools/perf/pmu-events/arch/x86/haswell/ |
| H A D | hsw-metrics.json | 643 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/drivers/clk/tegra/ |
| H A D | clk-dfll.c | 990 * characterized to keep the downstream device stable at any DVCO
|
| /linux/tools/perf/pmu-events/arch/x86/ivybridge/ |
| H A D | ivb-metrics.json | 722 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/Documentation/security/keys/ |
| H A D | core.rst | 867 of the KDF is returned to the caller. The KDF is characterized with
|
| /linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
| H A D | bdwde-metrics.json | 793 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | ivt-metrics.json | 743 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/broadwell/ |
| H A D | bdw-metrics.json | 801 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/haswellx/ |
| H A D | hsx-metrics.json | 866 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
| H A D | bdx-metrics.json | 1024 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| H A D | rkl-metrics.json | 1333 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | icl-metrics.json | 1312 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/skylake/ |
| H A D | skl-metrics.json | 1194 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | tgl-metrics.json | 1333 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A D | clx-metrics.json | 1546 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | skx-metrics.json | 1494 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | icx-metrics.json | 1665 …he L1D. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
| /linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | gnr-metrics.json | 1817 "PublicDescription": "This metric estimates how often the CPU was stalled without loads missing the L1 Data (L1D) cache. The L1D cache typically has the shortest latency. However; in certain cases like loads blocked on older stores; a load might suffer due to high latency even though it is being satisfied by the L1D. Another example is loads who miss in the TLB. These cases are characterized by execution unit stalls; while some non-completed demand load lives in the machine without having that demand load missing the L1 cache. Sample with: MEM_LOAD_RETIRED.L1_HIT. Related metrics: tma_clears_resteers, tma_machine_clears, tma_microcode_sequencer, tma_ms_switches, tma_ports_utilized_1",
|