From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: Re: [Xen-changelog] Create new vcpu_op() hypercall. Replaces old boot_vcpu() Date: Wed, 5 Oct 2005 10:28:48 +0100 Message-ID: <20051005092847.GE31971@uk.xensource.com> References: <20051003184236.GF29825@us.ibm.com> <20051004153828.GF17358@us.ibm.com> <20051004160544.GG17358@us.ibm.com> <7a928da7e42690192b2659cb33f5dc60@cl.cam.ac.uk> <20051004203920.GH17358@us.ibm.com> <20051004211005.GA31207@uk.xensource.com> <20051004211744.GI17358@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20051004211744.GI17358@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Oct 04, 2005 at 04:17:44PM -0500, Ryan Harper wrote: > The vcpu hotplug watch is triggered on any writes to /cpu. > It will then examine the node value to see if the change was made to > /cpu/cpu#/availability, (e.g. /cpu/1/availability), if the full path of > the change is correct, it examines the change values which are either > 'online' or 'offline' and invokes the vcpu_up/down handlers if the write > is a state change. > > I only ever see one trigger and the value is 'cpu' but I can confirm > that tdb sees the full write ('/cpu/1/availabilty', 'offline'). Thanks Ryan, that's been very helpful. This is now bug #280. Cheers, Ewan.