[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH 0/5] xen/domain: Cleanup to the domain_create() error paths
This is the start of a large amount of cleanup work to eventually allow for the removal of XEN_DOMCTL_max_cpus hypercall. The work to do is: 1) Make the domain destruction path fully idempotent, and use instead of the ad-hoc cleanup in each of the various create functions. 2) Do the same for the vcpu create/destroy path (which is in a far worse mess). The arch-specific ARM code is all idempotent, but the common and x86 code has a long way to go. With this done, we should be able to cleanly unwind from any failure at any point during domain creation, including when moving the vcpu allocation loop into domain_create(). Andrew Cooper (5): xen/domain: Prepare data for is_{pv,hvm}_domain() as early as possible xen/domain: Break __domain_destroy() out of domain_create() and complete_domain_destroy() xen/domain: Call lock_profile_deregister_struct() from common code xen/domain: Fold xsm_free_security_domain() paths together xen/domain: Make rangeset_domain_destroy() idempotent xen/arch/x86/domain.c | 1 - xen/common/domain.c | 62 +++++++++++++++++++++++++++++++-------------------- xen/common/rangeset.c | 3 +++ 3 files changed, 41 insertions(+), 25 deletions(-) -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |