Hi,
I'm working on adding CPU clock support to AARCH64. But I'm getting
messages like the following when I run --cpuclock-test :
cs: CPU clock mismatch (diff=158):
CPU 0: TSC=13558679258196, SEQ=383792
CPU 1: TSC=13558679258038, SEQ=383793
cs: CPU clock mismatch (diff=54):
CPU 0: TSC=13558679258924, SEQ=383850
CPU 1: TSC=13558679258870, SEQ=383851
cs: CPU clock mismatch (diff=52):
CPU 0: TSC=13558679259752, SEQ=383906
CPU 1: TSC=13558679259700, SEQ=383907
cs: Failed: 2772
Are these likely a problem with the platform, or something that can be
fixed in fio?
--
Rebecca
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html