From: George Dunlap <george.dunlap@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
<xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v2 05/10] libxl: event: Make libxl__poller_wakeup take a gc, not an egc
Date: Fri, 17 Jan 2020 12:30:52 +0000 [thread overview]
Message-ID: <fb68b456-8ce4-3a07-cfd3-1672ab9b55fc@citrix.com> (raw)
In-Reply-To: <20200113170843.21332-6-ian.jackson@eu.citrix.com>
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
next prev parent reply other threads:[~2020-01-17 12:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 17:08 [Xen-devel] [PATCH v2 00/10] libxl: event: Fix hang for some applications Ian Jackson
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 01/10] libxl: event: Rename poller.fds_changed to .fds_deregistered Ian Jackson
2020-01-17 11:07 ` George Dunlap
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 02/10] libxl: event: Rename ctx.pollers_fd_changed to .pollers_active Ian Jackson
2020-01-17 11:08 ` George Dunlap
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 03/10] libxl: event: Introduce CTX_UNLOCK_EGC_FREE Ian Jackson
2020-01-17 11:08 ` George Dunlap
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 04/10] libxl: event: Make LIBXL__EVENT_DISASTER take a gc, not an egc Ian Jackson
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 05/10] libxl: event: Make libxl__poller_wakeup " Ian Jackson
2020-01-17 12:30 ` George Dunlap [this message]
2020-01-17 13:46 ` Ian Jackson
2020-01-17 13:50 ` George Dunlap
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 06/10] libxl: event: Fix hang when mixing blocking and eventy calls Ian Jackson
2020-01-17 13:38 ` George Dunlap
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 07/10] libxl: event: poller pipe optimisation Ian Jackson
2020-01-17 12:06 ` George Dunlap
2020-01-17 13:41 ` Ian Jackson
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 08/10] libxl: event: Break out baton_wake Ian Jackson
2020-01-17 12:31 ` George Dunlap
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 09/10] libxl: event: Fix possible hang with libxl_osevent_beforepoll Ian Jackson
2020-01-17 13:39 ` George Dunlap
2020-01-13 17:08 ` [Xen-devel] [PATCH v2 10/10] libxl: event: Move poller pipe emptying to the end of afterpoll Ian Jackson
2020-01-17 12:32 ` George Dunlap
2020-01-17 14:24 ` Ian Jackson
2020-01-17 14:33 ` Ian Jackson
2020-01-17 14:39 ` George Dunlap
2020-01-17 14:34 ` George Dunlap
2020-01-17 13:40 ` [Xen-devel] [PATCH v2 00/10] libxl: event: Fix hang for some applications George Dunlap
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=fb68b456-8ce4-3a07-cfd3-1672ab9b55fc@citrix.com \
--to=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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).