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][resend] implementation of cpupool support in xl

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch][resend] implementation of cpupool support in xl
From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date: Thu, 16 Sep 2010 07:48:56 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 15 Sep 2010 22:49:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1284616139; x=1316152139; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; z=Message-ID:=20<4C91AFC8.8070600@xxxxxxxxxxxxxx>|Date:=20 Thu,=2016=20Sep=202010=2007:48:56=20+0200|From:=20Juergen =20Gross=20<juergen.gross@xxxxxxxxxxxxxx>|MIME-Version: =201.0|To:=20Ian=20Campbell=20<Ian.Campbell@xxxxxxxxxxxxx >|CC:=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xen-devel@list s.xensource.com>|Subject:=20Re:=20[Xen-devel]=20[Patch][r esend]=20implementation=20of=20cpupool=20support=0D=0A=20 in=20xl|References:=20<4C907510.3070904@xxxxxxxxxxxxxx> =09<1284539351.14311.18361.camel@xxxxxxxxxxxxxxxxxxxxxx> =09<4C9087B7.4090205@xxxxxxxxxxxxxx>=09<1284542187.14311. 18454.camel@xxxxxxxxxxxxxxxxxxxxxx>=09<4C90909F.7070700@t s.fujitsu.com>=09<1284543448.14311.18480.camel@xxxxxxxxxx ensource.com>=09<1284546138.14311.18568.camel@xxxxxxxxxxx nsource.com>=09<4C90ADC5.80202@xxxxxxxxxxxxxx>=20<1284564 937.16095.235.camel@xxxxxxxxxxxxxxxxxxxxxx>|In-Reply-To: =20<1284564937.16095.235.camel@xxxxxxxxxxxxxxxxxxxxxx>; bh=cuxcPBTi5xFa9c2cMDRDxxAEGTqkmTVcwIqSb2qQJBk=; b=KJ34RRdIjDSXmwSRjKfSCA6soDDM8owzLJQHc7dwm8/f0hCtiAxmOXye co/FoQghI82s8CyoAHezYtkCcjcrRE9UUmqMWf0ZRYPEFYtbepoQl/12c 1IWEd6gyzTg59pZSVQ8KLwPPFCtr/tZS4pvf/k9owdLLEH4deoi9O+y1R jWzuz0ZuZGDeHGBfFBKg/jJ1+MkAt5ydj8UMDyS1H8nOFcvFAIBESPW26 S8GcmqjjGyejPs2o9L+wGZxtroCCr;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=j7ZJwsCbWfioLEZ6eGjSeuY9FrYIBSEWS5yBHwteKmNipl3gFjVla7pm EYi32S8JEf50pTEvRK4PGQwd4IkEGbZiyu0dcvZkrAzl7pOnghoDW1PmX R3J5xltYSoJhC+1l2QbC0ppo6eBTt0AQ2H2TBEbEAJovSWG3Sye76wXWe zxl6GLfPC7POcCjQxJRfcdOXR2wdgHt5uP3Bjxge42L81D8c6LIgfCIJU /muwtleeCHokmnkf/Rdd7wW2XfJPV;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1284564937.16095.235.camel@xxxxxxxxxxxxxxxxxxxxxx>
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: Fujitsu Technology Solutions
References: <4C907510.3070904@xxxxxxxxxxxxxx> <1284539351.14311.18361.camel@xxxxxxxxxxxxxxxxxxxxxx> <4C9087B7.4090205@xxxxxxxxxxxxxx> <1284542187.14311.18454.camel@xxxxxxxxxxxxxxxxxxxxxx> <4C90909F.7070700@xxxxxxxxxxxxxx> <1284543448.14311.18480.camel@xxxxxxxxxxxxxxxxxxxxxx> <1284546138.14311.18568.camel@xxxxxxxxxxxxxxxxxxxxxx> <4C90ADC5.80202@xxxxxxxxxxxxxx> <1284564937.16095.235.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100805 Iceowl/1.0b1 Icedove/3.0.6
On 09/15/10 17:35, Ian Campbell wrote:
I'm afraid I think you do need to cycle through the elements calling
libxl_poolinfo_destroy on each, this is consistent with how all other
libxl types are handled and means that users of the library are isolated
from a certain amount of change to the underlying types.

Often you can destroy each element as you walk over the list doing
whatever it is you needed the list for, for example see how
xl_cmdimpl.c:print_domain_vcpuinfo does it. libxl_list_vcpu has
basically the same semantics as libxl_list_pool should have.

Okay, new patch attached.


Juergen

--
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

Attachment: xl-pools.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>