Hello! > > v4 => v5: > > - Adapted to new API by Peter Maydell, Marc Zyngier and Christoffer Dall. > > Acked-by's on the documentation were dropped, just in case, because i > > slightly adjusted it. Additionally, i merged all doc updates into one > > patch. > > Could you tell us what you changed in the doc patch from the version > that got sent out with the acks, please?
Sorry, completely forgot to answer this one... The major differences / things to review are: 1. Both GICv2 and GICv3 use the same value of KVM_DEV_ARM_VGIC_CPUID_MASK, which is extended to 32 bits. So GICv2 attribute layout also looks like: --- cut --- bits: | 63 .... 32 | 31 .... 0 | values: | vcpu_index | offset | --- cut --- 2. KVM_DEV_ARM_VGIC_CPU_SYSREGS documentation originally says (error code description): --- cut --- -EBUSY: One or more VCPUs are running --- cut --- While my version says "VCPU is running". Since this is CPU interface, it does not affect other CPUs, so for simplicity i check only current vCPU in my code. That's all. Just i'm maybe too careful about fundamentals... Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html