libxl: fixes related to concurrency improvements
cover libxl: fixes related to concurrency improvements
While reviving old patches to add job support to the libxl driver, testing revealed some problems that were difficult to encounter in the current, more serialized processing approach used in the driver.
The first patch is a bug fix, plugging leaks of libxlDomainObjPrivate objects. The second patch removes the list of libxl timer registrations maintained in the driver - a hack I was never fond of. The third patch moves domain shutdown handling to a thread, instead of doing all the shutdown work in the event handler. The fourth patch fixes an issue wrt child process handling discussed in this thread
http://lists.xen.org/archives/html/xen-devel/2014-01/msg01553.html
Ian Jackson's latest patches on the libxl side are here
http://lists.xen.org/archives/html/xen-devel/2014-02/msg00124.html
Jim Fehlig (4):
libxl: fix leaking libxlDomainObjPrivate
libxl: remove list of timer registrations from libxlDomainObjPrivate
libxl: handle domain shutdown events in a thread
libxl: improve subprocess handling
src/libxl/libxl_conf.h | 5 +- src/libxl/libxl_domain.c | 102 ++++++++--------------------------- src/libxl/libxl_domain.h | 8 +-- src/libxl/libxl_driver.c | 135 +++++++++++++++++++++++++++++++---------------- 4 files changed, 115 insertions(+), 135 deletions(-)
Signature · 1 line
1.8.1.4
PATCH 1/4 libxl: fix leaking libxlDomainObjPrivate
When libxl registers an FD with the libxl driver, the refcnt of the associated libxlDomainObjPrivate object is incremented. The refcnt is decremented when libxl deregisters the FD. But some FDs are only deregistered when their libxl ctx is freed, which unfortunately is done in the libxlDomainObjPrivate dispose function. With references held by the FDs, libxlDomainObjPrivate is never disposed.
I added the ref/unref in FD registration/deregistration when adding the same in timer registration/deregistration. For timers, this is a simple approach to ensuring the libxlDomainObjPrivate is not disposed prior to their expirtation, which libxl guarantees will occur. It is not needed for FDs, and only causes libxlDomainObjPrivate to leak.
This patch removes the reference on libxlDomainObjPrivate for FD registrations, but retains them for timer registrations. Tested on the latest releases of Xen supported by the libxl driver: 4.2.3, 4.3.1, and 4.4.0 RC3.
--- src/libxl/libxl_domain.c | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-)
src/libxl/libxl_domain.c +10 -11
@@ -1,7 +1,7 @@/* * libxl_domain.c: libxl domain object private state * -* Copyright (C) 2011-2013 SUSE LINUX Products GmbH, Nuernberg, Germany. +* Copyright (C) 2011-2014 SUSE LINUX Products GmbH, Nuernberg, Germany. * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Lesser General Public
@@ -92,7 +92,13 @@ libxlDomainObjPrivateOnceInit(void)VIR_ONCE_GLOBAL_INIT (libxlDomainObjPrivate) static void -libxlDomainObjEventHookInfoFree (void *obj) +libxlDomainObjFDEventHookInfoFree (void *obj) +{ +VIR_FREE (obj); +} + +static void +libxlDomainObjTimerEventHookInfoFree (void *obj) {libxlEventHookInfoPtr info = obj;
@@ -138,12 +144,6 @@ libxlDomainObjFDRegisterEventHook(void *priv,return -1 ; info->priv = priv; -/* -* Take a reference on the domain object. Reference is dropped in -* libxlDomainObjEventHookInfoFree, ensuring the domain object outlives -* the fd event objects. -*/ -virObjectRef (info->priv); info->xl_priv = xl_priv;if (events &POLLIN )
@@ -152,9 +152,8 @@ libxlDomainObjFDRegisterEventHook(void *priv, vir_events |=VIR_EVENT_HANDLE_WRITABLE ; info->id =virEventAddHandle (fd, vir_events, libxlDomainObjFDEventCallback, - info, libxlDomainObjEventHookInfoFree); + info, libxlDomainObjFDEventHookInfoFree);if (info->id <0 ) { -virObjectUnref (info->priv);VIR_FREE (info);return -1 ; }
@@ -259,7 +258,7 @@ libxlDomainObjTimeoutRegisterEventHook(void *priv, timeout = res.tv_sec *1000 + (res.tv_usec +999 ) /1000 ; } info->id =virEventAddTimeout (timeout, libxlDomainObjTimerCallback, - info, libxlDomainObjEventHookInfoFree); + info, libxlDomainObjTimerEventHookInfoFree);if (info->id <0 ) {virObjectUnref (info->priv);VIR_FREE (info);
Signature · 1 line
1.8.1.4
PATCH 2/4 libxl: remove list of timer registrations from libxlDomainObjPrivate
In reply to Jim FehligDue to some misunderstanding of requirements libxl places on timer handling, I introduced the half-brained idea of maintaining a list of timeouts that the driver could force to expire before freeing a libxlDomainObjPrivate (and hence libxl_ctx). But testing all the latest versions of Xen supported by the libxl driver (4.2.3, 4.3.1, 4.4.0 RC3), I see that libxl will handle this just fine and there is no need to force expiration behind libxl's back. Indeed it may be harmful to do so.
This patch removes the timer list, allowing libxl to handle cleanup of its timer registrations.
--- src/libxl/libxl_conf.h | 5 +--- src/libxl/libxl_domain.c | 72 +++--------------------------------------------- src/libxl/libxl_domain.h | 8 +----- src/libxl/libxl_driver.c | 3 +- 4 files changed, 7 insertions(+), 81 deletions(-)
src/libxl/libxl_conf.h +1 -4
@@ -1,7 +1,7 @@/* * libxl_conf.h: libxl configuration management * -* Copyright (C) 2011-2013 SUSE LINUX Products GmbH, Nuernberg, Germany. +* Copyright (C) 2011-2014 SUSE LINUX Products GmbH, Nuernberg, Germany. * Copyright (C) 2011 Univention GmbH. * * This library is free software; you can redistribute it and/or
@@ -115,9 +115,6 @@ struct _libxlDriverPrivate {virSysinfoDefPtr hostsysinfo; }; -typedef struct _libxlEventHookInfo libxlEventHookInfo ; -typedef libxlEventHookInfo *libxlEventHookInfoPtr ; -# define LIBXL_SAVE_MAGIC "libvirt-xml\n \0 \r"# define LIBXL_SAVE_VERSION 1
src/libxl/libxl_domain.c +4 -68
100 lines not on this page · raw message
src/libxl/libxl_domain.h +1 -7
@@ -1,7 +1,7 @@/* * libxl_domain.h: libxl domain object private state * -* Copyright (C) 2011-2013 SUSE LINUX Products GmbH, Nuernberg, Germany. +* Copyright (C) 2011-2014 SUSE LINUX Products GmbH, Nuernberg, Germany. * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Lesser General Public
@@ -43,9 +43,6 @@ struct _libxlDomainObjPrivate {/* console */ virChrdevsPtr devs;libxl_evgen_domain_death *deathW; - -/* list of libxl timeout registrations */ -libxlEventHookInfoPtr timerRegistrations; };
@@ -56,7 +53,4 @@ extern virDomainDefParserConfig libxlDomainDefParserConfig;int libxlDomainObjPrivateInitCtx (virDomainObjPtr vm); -void -libxlDomainObjRegisteredTimeoutsCleanup (libxlDomainObjPrivatePtr priv); -#endif /* LIBXL_DOMAIN_H */
src/libxl/libxl_driver.c +1 -2
@@ -2,7 +2,7 @@* libxl_driver.c: core driver methods for managing libxenlight domains * * Copyright (C) 2006-2014 Red Hat, Inc. -* Copyright (C) 2011-2013 SUSE LINUX Products GmbH, Nuernberg, Germany. +* Copyright (C) 2011-2014 SUSE LINUX Products GmbH, Nuernberg, Germany. * Copyright (C) 2011 Univention GmbH. * * This library is free software; you can redistribute it and/or
@@ -313,7 +313,6 @@ libxlVmCleanup(libxlDriverPrivatePtr driver, vm->newDef =NULL ; } -libxlDomainObjRegisteredTimeoutsCleanup (priv);virObjectUnref (cfg); }
Signature · 1 line
1.8.1.4
PATCH 3/4 libxl: handle domain shutdown events in a thread
In reply to Jim FehligHandling the domain shutdown event within the event handler seems a bit unfair to libxl's event machinery. Domain "shutdown" could take considerable time. E.g. if the shutdown reason is reboot, the domain must be reaped and then started again.
Spawn a shutdown handler thread to do this work, allowing libxl's event machinery to go about its business.
--- src/libxl/libxl_driver.c | 132 ++++++++++++++++++++++++++++++++--------------- 1 file changed, 89 insertions(+), 43 deletions(-)
src/libxl/libxl_driver.c +89 -43
@@ -352,61 +352,107 @@ libxlVmReap(libxlDriverPrivatePtr driver,# define VIR_LIBXL_EVENT_CONST const#endif +struct libxlShutdownThreadInfo +{ +virDomainObjPtr vm; +libxl_event *event; +}; + +static void -libxlEventHandler(void *data, VIR_LIBXL_EVENT_CONST libxl_event *event) +libxlDomainShutdownThread (void *opaque) {libxlDriverPrivatePtr driver = libxl_driver; -libxlDomainObjPrivatePtr priv = ((virDomainObjPtr )data)->privateData; -virDomainObjPtr vm =NULL ; +struct libxlShutdownThreadInfo *shutdown_info = opaque; +virDomainObjPtr vm = shutdown_info->vm; +libxlDomainObjPrivatePtr priv = vm->privateData; +libxl_event *ev = shutdown_info->event; +libxl_ctx *ctx = priv->ctx;virObjectEventPtr dom_event =NULL ; -libxl_shutdown_reason xl_reason = event->u.domain_shutdown.shutdown_reason; - -if (event->type ==LIBXL_EVENT_TYPE_DOMAIN_SHUTDOWN ) { -virDomainShutoffReason reason; - -/* -* Similar to the xl implementation, ignore SUSPEND. Any actions needed -* after calling libxl_domain_suspend() are handled by it's callers. -*/ -if (xl_reason ==LIBXL_SHUTDOWN_REASON_SUSPEND ) - goto cleanup; +libxl_shutdown_reason xl_reason = ev->u.domain_shutdown.shutdown_reason; +virDomainShutoffReason reason; - vm =virDomainObjListFindByID (driver->domains, event->domid); -if (!vm) - goto cleanup; +virObjectLock (vm); -switch (xl_reason) { -case LIBXL_SHUTDOWN_REASON_POWEROFF : -case LIBXL_SHUTDOWN_REASON_CRASH : -if (xl_reason ==LIBXL_SHUTDOWN_REASON_CRASH ) { - dom_event =virDomainEventLifecycleNewFromObj (vm, -VIR_DOMAIN_EVENT_STOPPED , -VIR_DOMAIN_EVENT_STOPPED_CRASHED ); - reason =VIR_DOMAIN_SHUTOFF_CRASHED ; - }else { - reason =VIR_DOMAIN_SHUTOFF_SHUTDOWN ; - } -libxlVmReap (driver, vm, reason); -if (!vm->persistent) { -virDomainObjListRemove (driver->domains, vm); - vm =NULL ; - } -break ; -case LIBXL_SHUTDOWN_REASON_REBOOT : -libxlVmReap (driver, vm,VIR_DOMAIN_SHUTOFF_SHUTDOWN ); -libxlVmStart (driver, vm,0 ,-1 ); -break ; -default : -VIR_INFO ("Unhandled shutdown_reason %d" , xl_reason); -break ; - } +switch (xl_reason) { +case LIBXL_SHUTDOWN_REASON_POWEROFF : +case LIBXL_SHUTDOWN_REASON_CRASH : +if (xl_reason ==LIBXL_SHUTDOWN_REASON_CRASH ) { + dom_event =virDomainEventLifecycleNewFromObj (vm, +VIR_DOMAIN_EVENT_STOPPED , +VIR_DOMAIN_EVENT_STOPPED_CRASHED ); + reason =VIR_DOMAIN_SHUTOFF_CRASHED ; + }else { + reason =VIR_DOMAIN_SHUTOFF_SHUTDOWN ; + } +libxlVmReap (driver, vm, reason); +if (!vm->persistent) { +virDomainObjListRemove (driver->domains, vm); + vm =NULL ; + } +break ; +case LIBXL_SHUTDOWN_REASON_REBOOT : +libxlVmReap (driver, vm,VIR_DOMAIN_SHUTOFF_SHUTDOWN ); +libxlVmStart (driver, vm,0 ,-1 ); +break ; +default : +VIR_INFO ("Unhandled shutdown_reason %d" , xl_reason); +break ; } -cleanup:if (vm)virObjectUnlock (vm);if (dom_event)libxlDomainEventQueue (driver, dom_event); +libxl_event_free (ctx, ev); +VIR_FREE (shutdown_info); +} + +static void +libxlEventHandler(void *data, VIR_LIBXL_EVENT_CONST libxl_event *event) +{ +virDomainObjPtr vm = data; +libxlDomainObjPrivatePtr priv = vm->privateData; +libxl_shutdown_reason xl_reason = event->u.domain_shutdown.shutdown_reason; +struct libxlShutdownThreadInfo *shutdown_info; +virThread thread; + +if (event->type !=LIBXL_EVENT_TYPE_DOMAIN_SHUTDOWN ) { +VIR_INFO ("Unhandled event type %d" , event->type); + goto cleanup; + } + +/* +* Similar to the xl implementation, ignore SUSPEND. Any actions needed +* after calling libxl_domain_suspend() are handled by it's callers. +*/ +if (xl_reason ==LIBXL_SHUTDOWN_REASON_SUSPEND ) + goto cleanup; + +/* +* Start a thread to handle shutdown. We don't want to be tying up +* libxl's event machinery by doing a potentially lengthy shutdown. +*/ +if (VIR_ALLOC (shutdown_info) <0 ) + goto cleanup; + + shutdown_info->vm = data; + shutdown_info->event = (libxl_event *)event; +if (virThreadCreate (&thread, true, libxlDomainShutdownThread, + shutdown_info) <0 ) { +/* +* Not much we can do on error here except log it. +*/ +VIR_ERROR (_ ("Failed to create thread to handle domain shutdown" )); + goto cleanup; + } + +/* +* libxl_event freed in shutdown thread +*/ +return ; + +cleanup:/* Cast away any const */ libxl_event_free (priv->ctx, (libxl_event *)event); }
Signature · 1 line
1.8.1.4
Re: [libvirt] [PATCH 3/4] libxl: handle domain shutdown events in a thread
Quoted 142 lines · Jim Fehlig
Handling the domain shutdown event within the event handler seems a bit unfair to libxl's event machinery. Domain "shutdown" could take considerable time. E.g. if the shutdown reason is reboot, the domain must be reaped and then started again.
Spawn a shutdown handler thread to do this work, allowing libxl's event machinery to go about its business.
Signed-off-by Jim Fehlig <[email protected]>--- src/libxl/libxl_driver.c | 132 ++++++++++++++++++++++++++++++++--------------- 1 file changed, 89 insertions(+), 43 deletions(-)src/libxl/libxl_driver.c +66
-43@@ -352,61 +352,107 @@ libxlVmReap(libxlDriverPrivatePtr driver,# define VIR_LIBXL_EVENT_CONST const#endif +struct libxlShutdownThreadInfo +{ +virDomainObjPtr vm; +libxl_event *event; +}; + +static void -libxlEventHandler(void *data, VIR_LIBXL_EVENT_CONST libxl_event *event) +libxlDomainShutdownThread (void *opaque) {libxlDriverPrivatePtr driver = libxl_driver; -libxlDomainObjPrivatePtr priv = ((virDomainObjPtr )data)->privateData; -virDomainObjPtr vm =NULL ; +struct libxlShutdownThreadInfo *shutdown_info = opaque; +virDomainObjPtr vm = shutdown_info->vm; +libxlDomainObjPrivatePtr priv = vm->privateData; +libxl_event *ev = shutdown_info->event; +libxl_ctx *ctx = priv->ctx;virObjectEventPtr dom_event =NULL ; -libxl_shutdown_reason xl_reason = event->u.domain_shutdown.shutdown_reason; - -if (event->type ==LIBXL_EVENT_TYPE_DOMAIN_SHUTDOWN ) { -virDomainShutoffReason reason; - -/* -* Similar to the xl implementation, ignore SUSPEND. Any actions needed -* after calling libxl_domain_suspend() are handled by it's callers. -*/ -if (xl_reason ==LIBXL_SHUTDOWN_REASON_SUSPEND ) - goto cleanup; +libxl_shutdown_reason xl_reason = ev->u.domain_shutdown.shutdown_reason; +virDomainShutoffReason reason; - vm =virDomainObjListFindByID (driver->domains, event->domid); -if (!vm) - goto cleanup; +virObjectLock (vm); -switch (xl_reason) { -case LIBXL_SHUTDOWN_REASON_POWEROFF : -case LIBXL_SHUTDOWN_REASON_CRASH : -if (xl_reason ==LIBXL_SHUTDOWN_REASON_CRASH ) { - dom_event =virDomainEventLifecycleNewFromObj (vm, -VIR_DOMAIN_EVENT_STOPPED , -VIR_DOMAIN_EVENT_STOPPED_CRASHED ); - reason =VIR_DOMAIN_SHUTOFF_CRASHED ; - }else { - reason =VIR_DOMAIN_SHUTOFF_SHUTDOWN ; - } -libxlVmReap (driver, vm, reason); -if (!vm->persistent) { -virDomainObjListRemove (driver->domains, vm); - vm =NULL ; - } -break ; -case LIBXL_SHUTDOWN_REASON_REBOOT : -libxlVmReap (driver, vm,VIR_DOMAIN_SHUTOFF_SHUTDOWN ); -libxlVmStart (driver, vm,0 ,-1 ); -break ; -default : -VIR_INFO ("Unhandled shutdown_reason %d" , xl_reason); -break ; - } +switch (xl_reason) { +case LIBXL_SHUTDOWN_REASON_POWEROFF : +case LIBXL_SHUTDOWN_REASON_CRASH : +if (xl_reason ==LIBXL_SHUTDOWN_REASON_CRASH ) { + dom_event =virDomainEventLifecycleNewFromObj (vm, +VIR_DOMAIN_EVENT_STOPPED , +VIR_DOMAIN_EVENT_STOPPED_CRASHED ); + reason =VIR_DOMAIN_SHUTOFF_CRASHED ; + }else { + reason =VIR_DOMAIN_SHUTOFF_SHUTDOWN ; + } +libxlVmReap (driver, vm, reason); +if (!vm->persistent) { +virDomainObjListRemove (driver->domains, vm); + vm =NULL ; + } +break ; +case LIBXL_SHUTDOWN_REASON_REBOOT : +libxlVmReap (driver, vm,VIR_DOMAIN_SHUTOFF_SHUTDOWN ); +libxlVmStart (driver, vm,0 ,-1 ); +break ; +default : +VIR_INFO ("Unhandled shutdown_reason %d" , xl_reason); +break ; } -cleanup:if (vm)virObjectUnlock (vm);if (dom_event)libxlDomainEventQueue (driver, dom_event); +libxl_event_free (ctx, ev); +VIR_FREE (shutdown_info); +} + +static void +libxlEventHandler(void *data, VIR_LIBXL_EVENT_CONST libxl_event *event) +{ +virDomainObjPtr vm = data; +libxlDomainObjPrivatePtr priv = vm->privateData; +libxl_shutdown_reason xl_reason = event->u.domain_shutdown.shutdown_reason; +struct libxlShutdownThreadInfo *shutdown_info; +virThread thread; + +if (event->type !=LIBXL_EVENT_TYPE_DOMAIN_SHUTDOWN ) { +VIR_INFO ("Unhandled event type %d" , event->type); + goto cleanup; + } + +/* +* Similar to the xl implementation, ignore SUSPEND. Any actions needed +* after calling libxl_domain_suspend() are handled by it's callers. +*/ +if (xl_reason ==LIBXL_SHUTDOWN_REASON_SUSPEND ) + goto cleanup; + +/*
src/libxl/libxl_driver.c libxlVmReap(libxlDriverPrivatePtr driver, · line 442
Quoted 10 lines
src/libxl/libxl_driver.c +10
-0+* Start a thread to handle shutdown. We don't want to be tying up +* libxl's event machinery by doing a potentially lengthy shutdown. +*/ +if (VIR_ALLOC (shutdown_info) <0 ) + goto cleanup; + + shutdown_info->vm = data; + shutdown_info->event = (libxl_event *)event; +if (virThreadCreate (&thread, true, libxlDomainShutdownThread, + shutdown_info) <0 ) {
The 2nd argument 'true' tells, if @thread is joinable. Since you are not joining it anywhere, I guess it should be rather 'false'. Moreover, it will avoid some memory leaks, as pthread free()-s memory needed for thread itself (otherwise the memory would be free()-d in phtread_join - which again is not called anywhere).
src/libxl/libxl_driver.c libxlVmReap(libxlDriverPrivatePtr driver, · line 455
Quoted 13 lines
src/libxl/libxl_driver.c +13
-0+/* +* Not much we can do on error here except log it. +*/ +VIR_ERROR (_ ("Failed to create thread to handle domain shutdown" )); + goto cleanup; + } + +/* +* libxl_event freed in shutdown thread +*/ +return ; + +cleanup:
Since this is in fact an error path, I suggest renaming the label to 'error'.
src/libxl/libxl_driver.c libxlVmReap(libxlDriverPrivatePtr driver, · line 458
Quoted 4 lines
src/libxl/libxl_driver.c +0
-0/* Cast away any const */ libxl_event_free (priv->ctx, (libxl_event *)event); }
ACK if you fix these two issues.
Michal
PATCH 4/4 libxl: improve subprocess handling
In reply to Jim FehligIf available, let libxl handle reaping any children it creates by specifying libxl_sigchld_owner_libxl_always_selective_reap. This feature was added to improve subprocess handling in libxl when used in an application that does not install a SIGCHLD handler like libvirt
http://lists.xen.org/archives/html/xen-devel/2014-01/msg01555.html
Prior to this patch, it is possible to hit asserts in libxl when reaping subprocesses, particularly during simultaneous operations on multiple domains. With this patch, and the corresponding changes to libxl, I no longer see the asserts.
---
The libxl patch has not yet hit xen.git, but without it this patch has no semantic change, only explicitly setting chldowner to the default of libxl_sigchld_owner_libxl.
src/libxl/libxl_domain.c | 9 +++++++++ 1 file changed, 9 insertions(+)
src/libxl/libxl_domain.c +9 -0
@@ -358,6 +358,14 @@ virDomainDefParserConfig libxlDomainDefParserConfig = { .devicesPostParseCallback = libxlDomainDeviceDefPostParse, }; +static const libxl_childproc_hooks libxl_child_hooks = { +#ifdef LIBXL_HAVE_SIGCHLD_OWNER_SELECTIVE_REAP + .chldowner = libxl_sigchld_owner_libxl_always_selective_reap, +#else + .chldowner = libxl_sigchld_owner_libxl, +#endif +}; +int libxlDomainObjPrivateInitCtx (virDomainObjPtr vm) {
@@ -395,6 +403,7 @@ libxlDomainObjPrivateInitCtx(virDomainObjPtr vm) }libxl_osevent_register_hooks (priv->ctx, &libxl_event_callbacks, priv); +libxl_childproc_setmode (priv->ctx, &libxl_child_hooks, priv); ret =0 ;
Signature · 1 line
1.8.1.4
Quoted 25 lines · Jim Fehlig
While reviving old patches to add job support to the libxl driver, testing revealed some problems that were difficult to encounter in the current, more serialized processing approach used in the driver.
The first patch is a bug fix, plugging leaks of libxlDomainObjPrivate objects. The second patch removes the list of libxl timer registrations maintained in the driver - a hack I was never fond of. The third patch moves domain shutdown handling to a thread, instead of doing all the shutdown work in the event handler. The fourth patch fixes an issue wrt child process handling discussed in this thread
http://lists.xen.org/archives/html/xen-devel/2014-01/msg01553.html
Ian Jackson's latest patches on the libxl side are here
http://lists.xen.org/archives/html/xen-devel/2014-02/msg00124.html
Jim Fehlig (4):
libxl: fix leaking libxlDomainObjPrivate
libxl: remove list of timer registrations from libxlDomainObjPrivate
libxl: handle domain shutdown events in a thread
libxl: improve subprocess handling
Quoted 6 lines
src/libxl/libxl_conf.h | 5 +- src/libxl/libxl_domain.c | 102 ++++++++--------------------------- src/libxl/libxl_domain.h | 8 +-- src/libxl/libxl_driver.c | 135 +++++++++++++++++++++++++++++++---------------- 4 files changed, 115 insertions(+), 135 deletions(-)
ACK series but see my comment on 3/4 where I'm asking for a pair of fixes prior pushing.
Michal
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 34 lines · Michal Privoznik
Quoted 25 lines · Jim Fehlig
While reviving old patches to add job support to the libxl driver, testing revealed some problems that were difficult to encounter in the current, more serialized processing approach used in the driver.
The first patch is a bug fix, plugging leaks of libxlDomainObjPrivate objects. The second patch removes the list of libxl timer registrations maintained in the driver - a hack I was never fond of. The third patch moves domain shutdown handling to a thread, instead of doing all the shutdown work in the event handler. The fourth patch fixes an issue wrt child process handling discussed in this thread
http://lists.xen.org/archives/html/xen-devel/2014-01/msg01553.html
Ian Jackson's latest patches on the libxl side are here
http://lists.xen.org/archives/html/xen-devel/2014-02/msg00124.html
Jim Fehlig (4):
libxl: fix leaking libxlDomainObjPrivate
libxl: remove list of timer registrations from libxlDomainObjPrivate
libxl: handle domain shutdown events in a thread
libxl: improve subprocess handlingQuoted 7 lines
src/libxl/libxl_conf.h | 5 +- src/libxl/libxl_domain.c | 102 ++++++++--------------------------- src/libxl/libxl_domain.h | 8 +-- src/libxl/libxl_driver.c | 135 +++++++++++++++++++++++++++++++---------------- 4 files changed, 115 insertions(+), 135 deletions(-)
Quoted 2 lines
ACK series but see my comment on 3/4 where I'm asking for a pair of fixes prior pushing.
Thanks for pointing those out, especially creating the joinable thread that was never joined :). Fixed. I also added a note to the commit message of 4/4 stating that the fixes on the libxl side will be included in Xen 4.4.0
http://lists.xen.org/archives/html/xen-devel/2014-02/msg00463.html
Pushed series. Thanks!
Regards,
Jim