All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: libvir-list@redhat.com, xen-devel@lists.xen.org
Subject: Re: [libvirt] [PATCH 0/2] libxl: fix handling of fd and timer registrations
Date: Tue, 17 Feb 2015 21:08:52 -0700	[thread overview]
Message-ID: <54E41054.6070208@suse.com> (raw)
In-Reply-To: <54D8DE7A.7090006@suse.com>

Jim Fehlig wrote:
> Anthony PERARD wrote:
>   
>> On Mon, Feb 02, 2015 at 05:00:34PM -0700, Jim Fehlig wrote:
>>   
>>     
>>> This small series fixes some assertions we occasionally see in the
>>> libxl driver when running libvirt-TCK.  The assertions were due to
>>> races between destroying per-domain libxl_ctx and receiving fd and
>>> timer callbacks associated with them.  The races are masked by
>>> setting DEBUG loglevel in libvirtd.conf, so often missed by
>>> automated test setups that want DEBUG loglevel.
>>>
>>> Patch 1 actually fixes the assertions.  Patch2 fixes a stupid mistake.
>>> See the commit messages for details.
>>>
>>> Jim Fehlig (2):
>>>   libxl: fix fd and timer event handling
>>>   libxl: Move setup of child processing code to driver initialization
>>>
>>>  src/libxl/libxl_domain.c | 244 +----------------------------------------------
>>>  src/libxl/libxl_driver.c | 212 +++++++++++++++++++++++++++++++++++++++-
>>>  2 files changed, 212 insertions(+), 244 deletions(-)
>>>     
>>>       
>> Hi Jim,
>>
>> I gave a try to those two patches with OpenStack. Assuming I haven't make any
>> mistake, it make things worse.
>>   
>>     
>
> Thanks Anthony.  I've cooked up a simpler reproducer and will
> investigate.  I do think these patches are an improvement, but they've
> obviously uncovered a locking issue in the driver.
>   

Following Ian's suggestion, I've extended the series to drop the
per-domain libxl_ctx's altogether

https://www.redhat.com/archives/libvir-list/2015-February/msg00611.html

>   
>> Environment:
>>   Ubuntu 14.04
>>   with Xen package install (xen 4.4)
>>     

I tested the series with xen-unstable and Xen 4.4.1 + commits 2ffeb5d7,
4b9143e4, 5a968257, 60ce518a, 66bff9fd, 77a1bf37, f49f9b41, 6b5a5bba,
93699882d, f1335f0d, and 8bc64413.  If you are in a position to test the
series in a similar configuration, I'd like to hear your results.

Regards,
Jim

      reply	other threads:[~2015-02-18  4:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  0:00 [PATCH 0/2] libxl: fix handling of fd and timer registrations Jim Fehlig
2015-02-03  0:00 ` [PATCH 1/2] libxl: fix fd and timer event handling Jim Fehlig
2015-02-03  0:00 ` [PATCH 2/2] libxl: Move setup of child processing code to driver initialization Jim Fehlig
2015-02-06 12:32 ` [PATCH 0/2] libxl: fix handling of fd and timer registrations Anthony PERARD
2015-02-09 16:21   ` Jim Fehlig
2015-02-18  4:08     ` 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=54E41054.6070208@suse.com \
    --to=jfehlig@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=libvir-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.