Hello! > > + 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 Ops, my fault, forgot. :( However, it seems to be very simple. "cpu id" is actually an index, not a real affinity ID (see http://lxr.free-electrons.com/source/include/linux/kvm_host.h#L427). Would it be OK just to enlarge KVM_DEV_ARM_VGIC_CPUID_MASK? bits: | 63 | 62 .. 32 | 31 .... 0 | values: | size | cpu id | offset | I think 31 bits is more than enough for CPU index. And, since id is actually an index, may be we should fix up docs? 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
