Searched refs:correlation (Results 1 – 14 of 14) 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.
842 init_crandom(&q->reorder_cor, r->correlation); in get_reorder()850 init_crandom(&q->corrupt_cor, r->correlation); in get_corrupt()1170 reorder.correlation = q->reorder_cor.rho; in netem_dump()1175 corrupt.correlation = q->corrupt_cor.rho; in netem_dump()
608 __u32 correlation; member613 __u32 correlation; member
36 also carries additional metadata for time correlation, better
628 __u32 correlation; member633 __u32 correlation; member
489 __be64 correlation; member528 __be64 correlation; member
1969 vfc_cmd->correlation = cpu_to_be64((u64)evt); in ibmvfc_queuecommand()2787 tmf->correlation = cpu_to_be64((u64)evt); in ibmvfc_abort_task_set()
85 --vm-time-correlation[=OPTIONS]::
80 - Allows correlation between an instruction and events, such as TLB and cache miss. (Data source
1352 $ perf inject -i perf.data.kvm --vm-time-correlation=dry-run1368 $ perf inject -i perf.data.kvm --vm-time-correlation="dry-run 0xffffe42722c64c41"1370 Note the options for 'perf inject' --vm-time-correlation are:1380 $ perf inject -i perf.data.kvm --vm-time-correlation=0xffffe42722c64c41 --force1426 Note, this is essential to enable time correlation between host and guest machines.1479 $ perf inject -i guest-sideband-testing-host-perf.data --vm-time-correlation=dry-run1487 …$ perf inject -i guest-sideband-testing-host-perf.data --vm-time-correlation=0xfffffa6ae070cb20 --…
182 there may be little correlation between the old and new locations in
648 actual timestamp. To perform the correlation correctly between the
