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 v3 06/18] xen/pvcalls: handle commands from the frontend
Date: Mon, 12 Jun 2017 18:03:33 -0400 [thread overview]
Message-ID: <3f119021-c866-5138-fe4b-263befa377b2@oracle.com> (raw)
In-Reply-To: <1496431915-20774-6-git-send-email-sstabellini@kernel.org>
> +
> static void pvcalls_back_work(struct work_struct *work)
> {
> + struct pvcalls_fedata *priv = container_of(work,
> + struct pvcalls_fedata, register_work);
> + int notify, notify_all = 0, more = 1;
> + struct xen_pvcalls_request req;
> + struct xenbus_device *dev = priv->dev;
> +
> + while (more) {
> + while (RING_HAS_UNCONSUMED_REQUESTS(&priv->ring)) {
> + RING_COPY_REQUEST(&priv->ring,
> + priv->ring.req_cons++,
> + &req);
> +
> + if (!pvcalls_back_handle_cmd(dev, &req)) {
> + RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(
> + &priv->ring, notify);
> + notify_all += notify;
> + }
> + }
> +
> + if (notify_all)
> + notify_remote_via_irq(priv->irq);
> +
> + RING_FINAL_CHECK_FOR_REQUESTS(&priv->ring, more);
> + }
> }
>
> static irqreturn_t pvcalls_back_event(int irq, void *dev_id)
> {
> + struct xenbus_device *dev = dev_id;
> + struct pvcalls_fedata *priv = NULL;
> +
> + if (dev == NULL)
> + return IRQ_HANDLED;
> +
> + priv = dev_get_drvdata(&dev->dev);
> + if (priv == NULL)
> + return IRQ_HANDLED;
> +
> + /*
> + * TODO: a small theoretical race exists if we try to queue work
> + * after pvcalls_back_work checked for final requests and before
> + * it returns. The queuing will fail, and pvcalls_back_work
> + * won't do the work because it is about to return. In that
> + * case, we lose the notification.
> + */
> + queue_work(priv->wq, &priv->register_work);
Would queuing delayed work (if queue_work() failed) help? And canceling
it on next invocation of pvcalls_back_event()?
-boris
next prev parent reply other threads:[~2017-06-12 22:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 19:31 [PATCH v3 00/18] introduce the Xen PV Calls backend Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-06-12 21:19 ` Boris Ostrovsky
2017-06-02 19:31 ` [PATCH v3 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-06-12 21:27 ` Boris Ostrovsky
2017-06-02 19:31 ` [PATCH v3 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini
2017-06-12 22:03 ` Boris Ostrovsky [this message]
2017-06-14 21:03 ` Stefano Stabellini
2017-06-15 14:33 ` Boris Ostrovsky
2017-06-15 18:54 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-06-13 6:06 ` Juergen Gross
2017-06-14 0:46 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-06-13 6:17 ` Juergen Gross
2017-06-14 0:46 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 09/18] xen/pvcalls: implement bind command Stefano Stabellini
2017-06-13 7:00 ` Juergen Gross
2017-06-14 0:46 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-06-13 7:00 ` Juergen Gross
2017-06-02 19:31 ` [PATCH v3 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-06-13 7:24 ` Juergen Gross
2017-06-14 0:47 ` Stefano Stabellini
2017-06-14 6:32 ` Juergen Gross
2017-06-14 19:27 ` Stefano Stabellini
2017-06-15 6:58 ` Juergen Gross
2017-06-15 17:54 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-06-13 7:28 ` Juergen Gross
2017-06-14 0:47 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-06-13 7:39 ` Juergen Gross
2017-06-14 0:47 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-06-13 7:49 ` Juergen Gross
2017-06-14 0:54 ` Stefano Stabellini
2017-06-14 13:51 ` Boris Ostrovsky
2017-06-14 19:15 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini
2017-06-13 7:51 ` Juergen Gross
2017-06-14 0:56 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-06-13 7:56 ` Juergen Gross
2017-06-14 0:57 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-06-13 7:59 ` Juergen Gross
2017-06-14 1:00 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini
2017-06-13 6:02 ` Juergen Gross
2017-06-13 23:46 ` Stefano Stabellini
2017-06-12 21:17 ` [PATCH v3 01/18] xen: introduce the pvcalls interface header Boris Ostrovsky
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=3f119021-c866-5138-fe4b-263befa377b2@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
Powered by JetHome