Re: [Xen-devel] libxl: error handling before xenstored runs

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Gianni Tedesco writes ("Re: [Xen-devel] libxl: error handling before xenstored 
runs"):
> I suppose it's because we don't want to be killable after sending the
> message but before receiving the reply, since the ring is going to get
> jammed up due to nobody consuming the reply. The reply that in this case
> never comes, but the kernel can't know that it won't eventually come,
> right?

The bookkeeping for the fact that there is a command outstanding
should take care of that problem - when matching up the replies with
requests it will find that the caller for the request has gone away
and discard the reply.  (Obviously it doesn't atm because the whole
thing is synchronous.)

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel