On 7 May 2014 16:20, Marc Zyngier <marc.zyngier@xxxxxxx> wrote: > This patch series adds debug support, a key feature missing from the > KVM/arm64 port. > > The main idea is to keep track of whether the debug registers are > "dirty" (changed by the guest) or not. In this case, perform the usual > save/restore dance, for one run only. It means we only have a penalty > if a guest is actually using the debug registers. > > The huge amount of registers is properly frightening, but CPUs > actually only implement a subset of them. Also, there is a number of > registers we don't bother emulating (things having to do with external > debug and OSlock). Presumably these registers now appear in the userspace interface too, yes? Did you check that they all cope with the "migration reads all register values on the source and then writes them on the destination in arbitrary order" semantics without further fiddling? (I have a note that says that at least OSLAR_EL1/OSLSR_EL1 won't work that way, for instance.) thanks -- PMM _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
