>> @@ -136,6 +136,9 @@ int kvm_dev_ioctl_check_extension(long ext) >> case KVM_CAP_SYNC_REGS: >> r = 1; >> break; >> + case KVM_CAP_NR_VCPUS: >> + r = KVM_MAX_VCPUS; >> + break; >> default: >> r = 0; >> } > > This looks like a bugfix, but having survived so long without it, I > imagine it's not urgent for 3.4.
Right it is not urgent. > btw, a better place might be in kvm_devel_ioctl_check_extension_generic(). Possibly yes. Dont know if there are architecture specific reasons to use something different than KVM_MAX_VCPUS. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
