| /openbmc/linux/tools/include/uapi/linux/ |
| H A D | pkt_sched.h | 601 __u32 delay_corr; /* delay correlation */
602 __u32 loss_corr; /* packet loss correlation */
603 __u32 dup_corr; /* duplicate correlation */
608 __u32 correlation; member
613 __u32 correlation; member
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | pkt_sched.h | 622 __u32 delay_corr; /* delay correlation */
623 __u32 loss_corr; /* packet loss correlation */
624 __u32 dup_corr; /* duplicate correlation */
629 __u32 correlation; member
634 __u32 correlation; member
|
| /openbmc/linux/drivers/hwtracing/stm/ |
| H A D | Kconfig | 35 also carries additional metadata for time correlation, better
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-uvc.rst | 43 close as possible to the above timestamp to enable correlation between
|
| H A D | dev-raw-vbi.rst | 129 towards the black level. Do not assume any other correlation of
|
| /openbmc/linux/Documentation/trace/ |
| H A D | sys-t.rst | 9 provides better trace source identification and timestamp correlation.
|
| /openbmc/linux/net/sched/ |
| H A D | sch_netem.c | 43 packets and add random jitter (and correlation). The random
195 if (!state || state->rho == 0) /* no correlation */ in get_crandom()
863 init_crandom(&q->reorder_cor, r->correlation); in get_reorder()
871 init_crandom(&q->corrupt_cor, r->correlation); in get_corrupt()
1201 reorder.correlation = q->reorder_cor.rho; in netem_dump()
1206 corrupt.correlation = q->corrupt_cor.rho; in netem_dump()
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 225 | 4 # Test vmdk backing file correlation
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/ |
| H A D | EthernetInterface.interface.yaml | 134 not have a 1:1 correlation to the systemd.network configuration file
|
| /openbmc/u-boot/drivers/usb/musb-new/ |
| H A D | musb_dma.h | 29 * - Knowing the correlation between dma channels and the
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-inject.txt | 85 --vm-time-correlation[=OPTIONS]::
|
| H A D | perf-intel-pt.txt | 1256 (i.e. no TSC timestamps) or VM Time Correlation. VM Time Correlation is an extra step
1332 Example using VM Time Correlation
1372 $ perf inject -i perf.data.kvm --vm-time-correlation=dry-run
1388 $ perf inject -i perf.data.kvm --vm-time-correlation="dry-run 0xffffe42722c64c41"
1390 Note the options for 'perf inject' --vm-time-correlation are:
1400 $ perf inject -i perf.data.kvm --vm-time-correlation=0xffffe42722c64c41 --force
1446 Note, this is essential to enable time correlation between host and guest machines.
1499 $ perf inject -i guest-sideband-testing-host-perf.data --vm-time-correlation=dry-run
1507 …$ perf inject -i guest-sideband-testing-host-perf.data --vm-time-correlation=0xfffffa6ae070cb20 --…
|
| H A D | perf-arm-spe.txt | 80 - Allows correlation between an instruction and events, such as TLB and cache miss. (Data source
|
| /openbmc/linux/tools/perf/util/ |
| H A D | auxtrace.h | 102 * @vm_time_correlation: perform VM Time Correlation
103 * @vm_tm_corr_dry_run: VM Time Correlation dry-run
104 * @vm_tm_corr_args: VM Time Correlation implementation-specific arguments
|
| /openbmc/linux/drivers/misc/echo/ |
| H A D | echo.h | 63 - The transmitted signal has poor self-correlation.
|
| /openbmc/linux/drivers/usb/musb/ |
| H A D | musb_dma.h | 29 * - Knowing the correlation between dma channels and the
|
| /openbmc/linux/drivers/scsi/ibmvscsi/ |
| H A D | ibmvfc.h | 489 __be64 correlation; member
528 __be64 correlation; member
|
| /openbmc/linux/drivers/media/platform/renesas/rcar-vin/ |
| H A D | rcar-vin.h | 139 * There is no correlation between channel number and CSI-2 VC. It's
|
| /openbmc/linux/arch/x86/events/amd/ |
| H A D | brs.c | 117 * Otherwise the correlation with the event's period is even in amd_brs_hw_config()
|
| /openbmc/linux/Documentation/devicetree/bindings/interconnect/ |
| H A D | samsung,exynos-bus.yaml | 46 Detailed correlation between sub-blocks and power line according
|
| /openbmc/qemu/accel/tcg/ |
| H A D | icount-common.c | 161 * Correlation between real and virtual time is always going to be
|
| /openbmc/linux/drivers/pci/hotplug/ |
| H A D | rpaphp_core.c | 192 * correlation, and obtain/validate the requested properties.
|
| /openbmc/linux/drivers/net/ieee802154/ |
| H A D | cc2520.c | 584 * correlation value provided by the radio) must be scaled to in cc2520_rx()
585 * the range 0-255. According to section 20.6, the correlation in cc2520_rx()
|
| /openbmc/linux/tools/perf/arch/arm64/util/ |
| H A D | arm-spe.c | 214 * also enable the timestamp tracing for samples correlation. in arm_spe_recording_options()
|
| /openbmc/linux/arch/riscv/kvm/ |
| H A D | vcpu_pmu.c | 576 * There is no correlation between the logical hardware counter and virtual counters. in kvm_riscv_vcpu_pmu_init()
|