Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754726AbcDYOPa (ORCPT ); Mon, 25 Apr 2016 10:15:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50965 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752190AbcDYOP2 (ORCPT ); Mon, 25 Apr 2016 10:15:28 -0400 Date: Mon, 25 Apr 2016 16:15:22 +0200 From: Radim =?utf-8?B?S3LEjW3DocWZ?= To: Greg Kurz Cc: Paolo Bonzini , james.hogan@imgtec.com, mingo@redhat.com, linux-mips@linux-mips.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, David Hildenbrand , qemu-ppc@nongnu.org, Cornelia Huck , Paul Mackerras , David Gibson Subject: Re: [PATCH v4 2/2] KVM: move vcpu id checking to archs Message-ID: <20160425141522.GB2386@potion> References: <146124809455.32509.15232948272580716135.stgit@bahia.huguette.org> <146124811255.32509.17679765789502091772.stgit@bahia.huguette.org> <20160421160018.GA31953@potion> <20160421184500.6cb5fd8a@bahia.huguette.org> <20160421173611.GB30356@potion> <20160422112538.41b23a9d@bahia.huguette.org> <20160422134029.GE25335@potion> <20160422165024.0d85d31d@bahia.huguette.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160422165024.0d85d31d@bahia.huguette.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 367 Lines: 10 2016-04-22 16:50+0200, Greg Kurz: > Just to be sure I haven't missed something: > - change the spec to introduce the MAX_VCPU_ID concept > - update all related checks in KVM > - provide a KVM_CAP_MAX_VCPU_ID for userspace That is it, thanks a lot! (From nitpicks that come to my mind ... MAX_VCPU_ID should not be able to lower the VCPU_ID limit below MAX_VCPUS.)