Searched refs:correlation (Results 1 – 11 of 11) sorted by relevance
43 close as possible to the above timestamp to enable correlation between
129 towards the black level. Do not assume any other correlation of
9 provides better trace source identification and timestamp correlation.
864 init_crandom(&q->reorder_cor, r->correlation); in get_reorder()872 init_crandom(&q->corrupt_cor, r->correlation); in get_corrupt()1202 reorder.correlation = q->reorder_cor.rho; in netem_dump()1207 corrupt.correlation = q->corrupt_cor.rho; in netem_dump()
499 __u32 correlation; member504 __u32 correlation; member
35 also carries additional metadata for time correlation, better
492 __be64 correlation; member531 __be64 correlation; member
2010 vfc_cmd->correlation = cpu_to_be64((u64)evt); in ibmvfc_queuecommand()2858 tmf->correlation = cpu_to_be64((u64)evt); in ibmvfc_abort_task_set()
85 --vm-time-correlation[=OPTIONS]::
1430 $ perf inject -i perf.data.kvm --vm-time-correlation=dry-run1446 $ perf inject -i perf.data.kvm --vm-time-correlation="dry-run 0xffffe42722c64c41"1448 Note the options for 'perf inject' --vm-time-correlation are:1458 $ perf inject -i perf.data.kvm --vm-time-correlation=0xffffe42722c64c41 --force1504 Note, this is essential to enable time correlation between host and guest machines.1557 $ perf inject -i guest-sideband-testing-host-perf.data --vm-time-correlation=dry-run1565 $ perf inject -i guest-sideband-testing-host-perf.data --vm-time-correlation=0xfffffa6ae070cb20 --force
350 information that was used in the evaluation. This then requires a correlation