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).
It seems we need to better distinguish between arch-specific and generic
definitions in the hvm subdirectory (even if it's just with comments to
indicate what is what) -- there is a lot of implicitly x86 stuff right now.
Also we may end up needing a clean arch-specific component to the Python xc
wrapper, although a few ifdef's are okay for now.
 -- Keir
On 8/12/06 8:36 pm, "Alex Williamson" <alex.williamson@xxxxxx> wrote:
> Hi Keir,
>
> Please pull:
>
> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg 
>
> This will add MCA support for ia64 enabling retrieval of firmware error
> logs by dom0, fixes for netback loaded as a module, fix a race with p2m
> table destruction, add xenoprof support, add /dev/mem support for
> running X, as well other fixes and additions that bring us up to date
> with xen-unstable. Thanks,
>
> Alex
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel