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] Remove vcpu_avail from the S-Expression that's p

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Remove vcpu_avail from the S-Expression that's passed on the wire
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 29 Mar 2006 13:55:09 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, Ryan Harper <ryanh@xxxxxxxxxx>
Delivery-date: Wed, 29 Mar 2006 12:56:12 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4429CA8B.8060100@xxxxxxxxxx>
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>
References: <4429918C.40502@xxxxxxxxxx> <4429CA8B.8060100@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 29 Mar 2006, at 00:45, Anthony Liguori wrote:

While looking into this bug, I realized that the vcpu_avail stuff in Xend is broken in general. If the guest uses sysfs for hotplugging, the vcpu_avail bitmap will be inconsistent. I've opened a bug in bugzilla about it that explains in more detail with my plan on how to clean this up for 3.0.3.

If the user uses sysfs to hotplug VCPUs, later calls to xm vcpu-set will result in the wrong thing happening. I don't think this is a show-stopper for 3.0.2 but we should at least document it.

If you think of the xenstore 'availability' keys as denoting which VCPUs are available for the guest to use if it wishes, but it doesn't necessarily need to have all online at the same time, then we do not need the guest kernel to update those fields in the xenstore. The current naming of those xenstore keys makes sense to me given the current semantics.

 -- Keir


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

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