From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 3/3] kvm-s390: implement KVM_CAP_MAX_VCPUS Date: Tue, 24 Apr 2012 16:01:40 +0300 Message-ID: <4F96A434.7030203@redhat.com> References: <1335252285-54213-1-git-send-email-borntraeger@de.ibm.com> <1335252285-54213-4-git-send-email-borntraeger@de.ibm.com> <4F969734.6080401@redhat.com> <4F96A0F4.1010205@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tossati , Carsten Otte , Alexander Graf , Jens Freimann , Cornelia Huck , Heiko Carstens , Martin Schwidefsky , Heinz Graalfs , KVM To: Christian Borntraeger Return-path: Received: from mx1.redhat.com ([209.132.183.28]:25790 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753977Ab2DXNCk (ORCPT ); Tue, 24 Apr 2012 09:02:40 -0400 In-Reply-To: <4F96A0F4.1010205@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 04/24/2012 03:47 PM, Christian Borntraeger wrote: > > 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. Okay, I'll fold the implementations unless something prevents it (unlikely). -- error compiling committee.c: too many arguments to function