[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: [Xen-changelog] Create new vcpu_op() hypercall. Replaces old boot_vcpu()

* Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx> [2005-10-03 
> # HG changeset patch
> # User kaf24@xxxxxxxxxxxxxxxxxxxx
> # Node ID 85f92475b9437fcd10bf1ae105f53b0abe963050
> # Parent  dd87869f877ca9c68c97f36b3870908fb279edb9
> Create new vcpu_op() hypercall. Replaces old boot_vcpu()
> hypercall and vcpu-related schedop commands.
> Signed-off-by: Keir Fraser <keir@xxxxxxxxxxxxx>

Both do_boot_vcpu() and now VCPU_CREATE rely on domU kernel playing nice
and not making the hypercall more than has been indicated in the shared
table when we built the domain (nr_vcpus).  Wouldn't it be better to
have the domain creation hypercall specify the number of vcpus for a
domain (as well as a cpumap to indicate which physical cpus are to be
used) and alloc vcpu structures at that point leaving the vcpu_ops() to
get context and unpause the vcpu?

If I put together a patch that mode the above change, would that be

Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.