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] "cpus" config parameter broken?

To: "dan.magenheimer@xxxxxxxxxx" <dan.magenheimer@xxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] "cpus" config parameter broken?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 09 Jan 2008 19:17:07 +0000
Delivery-date: Wed, 09 Jan 2008 11:19:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080109114030578.00000003216@djm-pc>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchRkyjajMDoVQVpQRWI8qTGrlL9cgABaF9AAFMFs1AAA9YWgw==
Thread-topic: [Xen-devel] "cpus" config parameter broken?
User-agent: Microsoft-Entourage/11.3.6.070618
On 9/1/08 18:40, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> My opinion: CPU affinity/restriction should NOT be preserved
> across migration.  Or if it is, it should only be preserved
> when the source and target have the same number of pcpus
> (thus allowing save/restore to work OK).  Or maybe it should
> only be preserved for save/restore and not for migration.
>>>>>>>>>>>> Comments? <<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I agree with that. Unless save/restore is on the same machine (identified in
some way) or at least has identical CPU topology as far as we can see.
Otherwise some higher-level entity needs to be smart enough to work out
affinity during restore and issue the correct 'xm' commands (or equivalent).

 -- Keir



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