From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: [PATCH][RESUBMIT] add dom0 vcpu hotplug control Date: Tue, 21 Jun 2005 12:02:20 +0100 Message-ID: <3d8eece205062104023b62ebe3@mail.gmail.com> References: <20050607220246.GD28421@us.ibm.com> <20050614163718.GB7954@us.ibm.com> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20050614163718.GB7954@us.ibm.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ryan Harper Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 6/14/05, Ryan Harper wrote: > * Ryan Harper [2005-06-07 17:05]: > > This patch adds new control messages for vcpu hotplug events. Via the > > xm vcpu_hotplug sub-program, VCPUS in domains can be enabled/disabled > > when CONFIG_HOTPLUG_CPU is enabled in the target domain's kernel. > > >=20 > Updated this patch to use vcpu_to_cpu up/down info to control whether > state changes are sent when hotplugging vcpus. I've applied both patches. I think there's a flaw in the way how vcpu_to_cpu gets passed up to python, the -1 -> # hack is kind of gross and it won't work for cpus > 9? Also the whole hotplug stuff is still missing interrupt re-routing when a vcpu is taken down. To do this, we need an evtchn operation to change the vcpu affinity of a port by changing notify_vcpu_id. christian