From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: linux-kernel@vger.kernel.org, jgross@suse.com,
Stefano Stabellini <stefano@aporeto.com>
Subject: Re: [PATCH v4 11/13] xen/pvcalls: implement poll command
Date: Fri, 22 Sep 2017 18:27:20 -0400 [thread overview]
Message-ID: <2ee745f7-5bf4-b45c-bee9-e8aa4c20de92@oracle.com> (raw)
In-Reply-To: <1505516440-11111-11-git-send-email-sstabellini@kernel.org>
>
> +static unsigned int pvcalls_front_poll_passive(struct file *file,
> + struct pvcalls_bedata *bedata,
> + struct sock_mapping *map,
> + poll_table *wait)
> +{
> + int notify, req_id, ret;
> + struct xen_pvcalls_request *req;
> +
> + if (test_bit(PVCALLS_FLAG_ACCEPT_INFLIGHT,
> + (void *)&map->passive.flags)) {
> + uint32_t req_id = READ_ONCE(map->passive.inflight_req_id);
> +
> + if (req_id != PVCALLS_INVALID_ID &&
> + READ_ONCE(bedata->rsp[req_id].req_id) == req_id)
> + return POLLIN | POLLRDNORM;
Do we need to clear PVCALLS_FLAG_ACCEPT_INFLIGHT? Or do we expect a
(subsequent?) accept() to do that?
-boris
> +
> + poll_wait(file, &map->passive.inflight_accept_req, wait);
> + return 0;
> + }
> +
next prev parent reply other threads:[~2017-09-22 22:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 23:00 [PATCH v4 00/13] introduce the Xen PV Calls frontend Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 01/13] xen/pvcalls: introduce the pvcalls xenbus frontend Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 02/13] xen/pvcalls: implement frontend disconnect Stefano Stabellini
2017-09-20 20:32 ` Boris Ostrovsky
2017-10-06 17:51 ` Stefano Stabellini
2017-10-06 20:21 ` Boris Ostrovsky
2017-10-06 20:29 ` Stefano Stabellini
2017-10-06 20:31 ` Boris Ostrovsky
2017-09-20 20:59 ` Boris Ostrovsky
2017-10-07 0:08 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 03/13] xen/pvcalls: connect to the backend Stefano Stabellini
2017-09-20 21:08 ` Boris Ostrovsky
2017-09-15 23:00 ` [PATCH v4 04/13] xen/pvcalls: implement socket command and handle events Stefano Stabellini
2017-09-21 17:42 ` Boris Ostrovsky
2017-10-06 18:38 ` Stefano Stabellini
2017-10-06 20:36 ` Boris Ostrovsky
2017-09-15 23:00 ` [PATCH v4 05/13] xen/pvcalls: implement connect command Stefano Stabellini
2017-09-21 18:28 ` Boris Ostrovsky
2017-10-06 17:44 ` Stefano Stabellini
2017-10-06 17:54 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 06/13] xen/pvcalls: implement bind command Stefano Stabellini
2017-09-21 19:40 ` Boris Ostrovsky
2017-10-06 20:35 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 07/13] xen/pvcalls: implement listen command Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 08/13] xen/pvcalls: implement accept command Stefano Stabellini
2017-09-22 0:00 ` Boris Ostrovsky
2017-10-06 22:06 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 09/13] xen/pvcalls: implement sendmsg Stefano Stabellini
2017-09-22 21:57 ` Boris Ostrovsky
2017-10-06 21:43 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 10/13] xen/pvcalls: implement recvmsg Stefano Stabellini
2017-09-22 22:05 ` Boris Ostrovsky
2017-10-06 20:46 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 11/13] xen/pvcalls: implement poll command Stefano Stabellini
2017-09-19 15:19 ` Andrea Parri
2017-10-06 23:33 ` Stefano Stabellini
2017-09-22 22:27 ` Boris Ostrovsky [this message]
2017-10-06 23:39 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 12/13] xen/pvcalls: implement release command Stefano Stabellini
2017-09-22 22:43 ` Boris Ostrovsky
2017-09-22 22:48 ` Boris Ostrovsky
2017-10-06 23:49 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 13/13] xen: introduce a Kconfig option to enable the pvcalls frontend Stefano Stabellini
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=2ee745f7-5bf4-b45c-bee9-e8aa4c20de92@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stefano@aporeto.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 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).