From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, xen-devel@lists.xenproject.org,
boris.ostrovsky@oracle.com, konrad.wilk@oracle.com,
perex@perex.cz, Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v2 3/5] ALSA: xen-front: Implement Xen event channel handling
Date: Tue, 24 Apr 2018 17:29:15 +0300 [thread overview]
Message-ID: <af277f77-5b22-58e3-4ea6-cde34e3181d3@gmail.com> (raw)
In-Reply-To: <s5ho9i8sn25.wl-tiwai@suse.de>
On 04/24/2018 05:20 PM, Takashi Iwai wrote:
> On Mon, 16 Apr 2018 08:24:51 +0200,
> Oleksandr Andrushchenko wrote:
>> +static irqreturn_t evtchnl_interrupt_req(int irq, void *dev_id)
>> +{
>> + struct xen_snd_front_evtchnl *channel = dev_id;
>> + struct xen_snd_front_info *front_info = channel->front_info;
>> + struct xensnd_resp *resp;
>> + RING_IDX i, rp;
>> + unsigned long flags;
>> +
>> + if (unlikely(channel->state != EVTCHNL_STATE_CONNECTED))
>> + return IRQ_HANDLED;
>> +
>> + spin_lock_irqsave(&front_info->io_lock, flags);
>> +
>> +again:
>> + rp = channel->u.req.ring.sring->rsp_prod;
>> + /* ensure we see queued responses up to rp */
>> + rmb();
>> +
>> + for (i = channel->u.req.ring.rsp_cons; i != rp; i++) {
> I'm not familiar with Xen stuff in general, but through a quick
> glance, this kind of code worries me a bit.
>
> If channel->u.req.ring.rsp_cons has a bogus number, this may lead to a
> very long loop, no? Better to have a sanity check of the ring buffer
> size.
In this loop I have:
resp = RING_GET_RESPONSE(&channel->u.req.ring, i);
and the RING_GET_RESPONSE macro is designed in the way that
it wraps around when *i* in the question gets bigger than
the ring size:
#define RING_GET_REQUEST(_r, _idx) \
(&((_r)->sring->ring[((_idx) & (RING_SIZE(_r) - 1))].req))
So, even if the counter has a bogus number it will not last long
>> +static irqreturn_t evtchnl_interrupt_evt(int irq, void *dev_id)
>> +{
>> + struct xen_snd_front_evtchnl *channel = dev_id;
>> + struct xen_snd_front_info *front_info = channel->front_info;
>> + struct xensnd_event_page *page = channel->u.evt.page;
>> + u32 cons, prod;
>> + unsigned long flags;
>> +
>> + if (unlikely(channel->state != EVTCHNL_STATE_CONNECTED))
>> + return IRQ_HANDLED;
>> +
>> + spin_lock_irqsave(&front_info->io_lock, flags);
>> +
>> + prod = page->in_prod;
>> + /* ensure we see ring contents up to prod */
>> + virt_rmb();
>> + if (prod == page->in_cons)
>> + goto out;
>> +
>> + for (cons = page->in_cons; cons != prod; cons++) {
> Ditto.
Same as above
>
> thanks,
>
> Takashi
Thank you,
Oleksandr
next prev parent reply other threads:[~2018-04-24 14:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 6:24 [PATCH v2 0/5] ALSA: xen-front: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
2018-04-16 6:24 ` [PATCH v2 1/5] ALSA: xen-front: Introduce Xen para-virtualized sound " Oleksandr Andrushchenko
2018-04-16 12:25 ` Juergen Gross
2018-04-17 8:24 ` Oleksandr Andrushchenko
2018-04-24 13:55 ` Takashi Iwai
2018-04-24 13:59 ` Oleksandr Andrushchenko
2018-04-16 6:24 ` [PATCH v2 2/5] ALSA: xen-front: Read sound driver configuration from Xen store Oleksandr Andrushchenko
2018-04-16 12:55 ` Juergen Gross
2018-04-17 8:42 ` Oleksandr Andrushchenko
2018-04-17 11:08 ` Juergen Gross
2018-04-16 6:24 ` [PATCH v2 3/5] ALSA: xen-front: Implement Xen event channel handling Oleksandr Andrushchenko
2018-04-16 13:12 ` Juergen Gross
2018-04-17 8:58 ` Oleksandr Andrushchenko
2018-04-17 11:14 ` Juergen Gross
2018-04-17 11:21 ` Oleksandr Andrushchenko
2018-04-16 13:53 ` kbuild test robot
2018-04-24 14:20 ` Takashi Iwai
2018-04-24 14:29 ` Oleksandr Andrushchenko [this message]
2018-04-24 14:35 ` Takashi Iwai
2018-04-24 14:58 ` Oleksandr Andrushchenko
2018-04-24 15:02 ` Takashi Iwai
2018-04-24 16:23 ` Oleksandr Andrushchenko
2018-04-25 8:26 ` Oleksandr Andrushchenko
2018-04-25 9:02 ` Takashi Iwai
2018-04-25 9:04 ` Oleksandr Andrushchenko
2018-04-16 6:24 ` [PATCH v2 4/5] ALSA: xen-front: Implement handling of shared buffers Oleksandr Andrushchenko
2018-04-16 13:39 ` Juergen Gross
2018-04-17 9:22 ` Oleksandr Andrushchenko
2018-04-17 11:15 ` Juergen Gross
2018-04-16 6:24 ` [PATCH v2 5/5] ALSA: xen-front: Implement ALSA virtual sound driver Oleksandr Andrushchenko
2018-04-16 14:09 ` Juergen Gross
2018-04-17 11:32 ` Oleksandr Andrushchenko
2018-04-17 12:26 ` Oleksandr Andrushchenko
2018-04-17 12:32 ` Juergen Gross
2018-04-17 12:34 ` Oleksandr Andrushchenko
2018-04-16 14:59 ` kbuild test robot
2018-04-17 12:42 ` [PATCH v2 0/5] ALSA: xen-front: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
2018-04-18 15:15 ` Oleksandr Andrushchenko
2018-04-23 6:34 ` Oleksandr Andrushchenko
2018-05-02 7:59 ` Oleksandr Andrushchenko
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=af277f77-5b22-58e3-4ea6-cde34e3181d3@gmail.com \
--to=andr2000@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--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).