|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2-resend 22/30] libxl: ocaml: event management [and 1 more messages]
Rob Hoes writes ("RE: [Xen-devel] [PATCH v2-resend 22/30] libxl:
ocaml: event management [and 1 more messages]"):
> [Ian Jackson:]
> > Have you considered this problem ?
>
> Yes, I have encountered such deadlocks, and got around them by
> making all calls into libxl mutually exclusive. This should mean
> that there can be only one thread at a time holding or waiting for
> the libxl lock, and I think that avoids the deadlock you
> described. It seems to be running smoothly now in our test setup.
I'm not sure how that would help. libxl already has a mutex which it
takes on entry, so all calls into libxl are already mututally
exclusive.
What would happen if your fd registration callback ocaml code tried to
make a libxl call ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |