From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Williamson <alex.williamson@hp.com>
Subject: Re: please pull xen-ia64-unstable.hg
Date: Thu, 14 Dec 2006 10:28:08 -0700
Message-ID: <1166117288.5666.6.camel@lappy>
References: <C1A06EE3.5982%Keir.Fraser@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C1A06EE3.5982%Keir.Fraser@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>, xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Sat, 2006-12-09 at 13:47 +0000, Keir Fraser wrote:
> Done. You shouldn't need HVM_PARAM_VCPUS: the tools have already
> setmaxvcpus, and this number is available to your HVM builder by doing a
> getdomaininfo and using max_vcpu_id (plus one). HVM params are really
> intended for registering values that Xen has some interest in -- which is
> not the case for this particular parameter (since it's redundant).

Hi Keir,

   Thanks for the advice, I fixed this to use getdomaininfo in our
current tree.  We also have two other tiny fixes in the tree that would
be nice to get in for 3.0.4.  Please pull the xen-ia64-unstable tree to
pick these up:
 
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.