Avi, This is the other part of the get_supported_cpuid change. We discussed it over IRC and you said it looks right. On Thu, 2011-11-17 at 12:18 +0200, Sasha Levin wrote: > If the amount of entries available passed to KVM_GET_SUPPORTED_CPUID is > too big we don't fail, we just adjust it to the amount actually needed > and fill the entries. > > Cc: Avi Kivity <avi@xxxxxxxxxx> > Cc: Marcelo Tosatti <mtosatti@xxxxxxxxxx> > Signed-off-by: Sasha Levin <levinsasha928@xxxxxxxxx> > --- > Documentation/virtual/kvm/api.txt | 7 +++---- > 1 files changed, 3 insertions(+), 4 deletions(-) > > diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt > index 7945b0b..273be09 100644 > --- a/Documentation/virtual/kvm/api.txt > +++ b/Documentation/virtual/kvm/api.txt > @@ -1074,10 +1074,9 @@ or for feature consistency across a cluster). > Userspace invokes KVM_GET_SUPPORTED_CPUID by passing a kvm_cpuid2 structure > with the 'nent' field indicating the number of entries in the variable-size > array 'entries'. If the number of entries is too low to describe the cpu > -capabilities, an error (E2BIG) is returned. If the number is too high, > -the 'nent' field is adjusted and an error (ENOMEM) is returned. If the > -number is just right, the 'nent' field is adjusted to the number of valid > -entries in the 'entries' array, which is then filled. > +capabilities, an error (E2BIG) is returned. If the number is above or just, > +right, the 'nent' field is adjusted to the number of valid entries in the > +'entries' array, which is then filled. > > The entries returned are the host cpuid as returned by the cpuid instruction, > with unknown or unsupported features masked out. Some features (for example, -- Sasha. -- 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
