On 18/07/2017 14:15, Andrew Jones wrote: >> >> If we want to add a "the platform provides a timer with 56 valid bits in >> the counter and compare register", then I think it should be a separate >> test, and the the user can see that "basic stuff works", "architecture >> compliance not so much" and shrug accordingly. > Two separate tests sounds good to me. Although, if the value of 'now' is > large enough that now + 10s will set bit 31, then a mustang run (at least > mine) will fail - and most likely cause a lot of confusion, since it > normally does not. We should probably attempt to address that known issue > in some way as well.
Is the value relative to vm startup or host startup? Paolo _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
