On 2 September 2015 at 09:09, Pavel Fedin <p.fedin@xxxxxxxxxxx> wrote: > The access is done similar to vGICv2, using KVM_DEV_ARM_VGIC_GRP_DIST_REGS > and KVM_DEV_ARM_VGIC_GRP_REDIST_REGS with KVM_SET_DEVICE_ATTR and > KVM_GET_DEVICE_ATTR ioctls. > > Some registers are 64-bit wide according to the specification. > KVM_DEV_ARM_VGIC_64BIT flag is introduced, allowing to perform full 64-bit > accesses. > > Signed-off-by: Pavel Fedin <p.fedin@xxxxxxxxxxx> > --- > + KVM_DEV_ARM_VGIC_GRP_REDIST_REGS > + Attributes: > + The attr field of kvm_device_attr encodes two values: > + bits: | 63 | 62 .. 40 | 39 .. 32 | 31 .... 0 | > + values: | size | reserved | cpu id | offset | We should avoid imposing an accidental limit on the maximum number of CPUs in the userspace API. GICv3 doesn't have a limit at 256 CPUs, so I think we should define an attr format which lets us specify a complete affinity specification. thanks -- PMM -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
