On 1/13/20 5:08 PM, Ian Jackson wrote: > We are going to want to call this in the following situation: > > * We have just set up an ao, which is to call back - so a > non-synchronous one. It ought not to call the application > back right away, so no egc. > > * There is a libxl thread blocking somewhere but it is using > using an out of date fd or timeout set, which does not take into > account the ao we have just started. > > * We try to wake that thread up, but libxl__poller_wakeup fails.
So the idea before was that these two functions take an egc, not so much because it actually uses the egc, but to make sure it's only called in a restricted set of conditions; and now we're relaxing those conditions? -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
