xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: libvir-list@redhat.com, xen-devel@lists.xen.org, bjzhang@suse.com
Subject: Re: [libvirt] [PATCH 0/4] libxl: fixes related to concurrency improvements
Date: Thu, 06 Feb 2014 10:36:26 -0700	[thread overview]
Message-ID: <52F3C81A.5080008@suse.com> (raw)
In-Reply-To: <52F385BE.5020509@redhat.com>

Michal Privoznik wrote:
> On 05.02.2014 18:39, Jim Fehlig wrote:
>> 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(-)
>>
>
> 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

      parent reply	other threads:[~2014-02-06 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 17:39 [PATCH 0/4] libxl: fixes related to concurrency improvements Jim Fehlig
2014-02-05 17:39 ` [PATCH 1/4] libxl: fix leaking libxlDomainObjPrivate Jim Fehlig
2014-02-05 17:39 ` [PATCH 2/4] libxl: remove list of timer registrations from libxlDomainObjPrivate Jim Fehlig
2014-02-05 17:39 ` [PATCH 3/4] libxl: handle domain shutdown events in a thread Jim Fehlig
2014-02-06 12:53   ` [libvirt] " Michal Privoznik
2014-02-05 17:39 ` [PATCH 4/4] libxl: improve subprocess handling Jim Fehlig
2014-02-06 12:53 ` [libvirt] [PATCH 0/4] libxl: fixes related to concurrency improvements Michal Privoznik
     [not found] ` <52F385BE.5020509@redhat.com>
2014-02-06 17:36   ` Jim Fehlig [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52F3C81A.5080008@suse.com \
    --to=jfehlig@suse.com \
    --cc=bjzhang@suse.com \
    --cc=libvir-list@redhat.com \
    --cc=mprivozn@redhat.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).