From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jes Sorensen <jes@sgi.com>
Subject: change in 'smp_cpus' at runtime vs vcpu_info?
Date: Fri, 26 Sep 2008 16:17:01 +0200
Message-ID: <48DCEEDD.4000901@sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from relay1.sgi.com ([192.48.171.29]:50520 "EHLO relay.sgi.com"
	rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
	id S1752061AbYIZORF (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 26 Sep 2008 10:17:05 -0400
Received: from eye3.emea.sgi.com (eye3.emea.sgi.com [144.253.156.24])
	by relay1.corp.sgi.com (Postfix) with ESMTP id 0E91D8F80E2
	for <kvm@vger.kernel.org>; Fri, 26 Sep 2008 07:17:02 -0700 (PDT)
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi,

Looking through the KVM qemu code, I see nothing that indicates that
smp_cpus can be increased after qemu is initially launched?

Does anyone see any reason why we couldn't allocate the vcpu_info
array at launch time based on the value of smp_cpus? Right now
vcpu_info is a static array and I would love to get rid of this
limitation if possible.

Cheers,
Jes