WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [xen-devel][PATCH v2][xend] save/restore cpu_weight and cpu_cap

To: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Subject: Re: [xen-devel][PATCH v2][xend] save/restore cpu_weight and cpu_cap
From: Andrew Jones <drjones@xxxxxxxxxx>
Date: Wed, 05 Aug 2009 15:34:41 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 05 Aug 2009 06:36:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18CA13DBCD74A1kanno.masaki@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Red Hat, Inc.
References: <1249040776.3750.13.camel@xxxxxxxxxxxxxxxxxxxxxxxxx> <1249043821.3750.20.camel@xxxxxxxxxxxxxxxxxxxxxxxxx> <18CA13DBCD74A1kanno.masaki@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Kan,

Thanks for catching my mess-up.  It looks like I messed-up and didn't
test on the tip.  So I completely missed changeset 19955, which corrects
the exact same issue I was attempting to correct.  Please disregard my
patch submittal.

Andrew


On Mon, 2009-08-03 at 10:43 +0900, Masaki Kanno wrote:
> Fri, 31 Jul 2009 14:37:01 +0200, Andrew Jones wrote:
> 
> >Argh... I shouldn't cut+paste patches into email editors.  Sending again
> >without allowing evil auto-wrap to mess with it.
> >
> 
> Hi Andrew,
> 
> Without your patch, I can save/restore cpu_weight and cpu_cap as follows.
> 
> # xm create vm1 cpu_weight=512 cpu_cap=100
> Using config file "/etc/xen/vm1".
> Started domain vm1 (id=1)
> # xm sched-credit -d vm1
> Name                                ID Weight  Cap
> vm1                                  1    512  100
> # xm list --long vm1 | grep cpu_
>     (cpu_weight 512)
>     (cpu_cap 100)
>     (cpu_time 22.504581706)
> # xm save vm1 /root/vm1.save
> # xm restore /root/vm1.save 
> # xm sched-credit -d vm1
> Name                                ID Weight  Cap
> vm1                                  2    512  100
> # xm list --long vm1 | grep cpu_
>     (cpu_weight 512)
>     (cpu_cap 100)
>     (cpu_time 2.200074199)
> 
> 
> What is your problem?
> How can I reproduce your problem?
> 
> FYI, can changeset 19955 help you?
> 
> Best regards,
>  Kan
> 
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>