From: Juergen Gross <jgross@suse.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, boris.ostrovsky@oracle.com,
konrad.wilk@oracle.com, perex@perex.cz, tiwai@suse.com
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v2 4/5] ALSA: xen-front: Implement handling of shared buffers
Date: Tue, 17 Apr 2018 13:15:51 +0200 [thread overview]
Message-ID: <7abbbaa0-93c7-5c93-d653-ed5a04199f6e@suse.com> (raw)
In-Reply-To: <edbd53c6-3396-9293-4a04-2b22655eeb12@gmail.com>
On 17/04/18 11:22, Oleksandr Andrushchenko wrote:
> On 04/16/2018 04:39 PM, Juergen Gross wrote:
>> On 16/04/18 08:24, Oleksandr Andrushchenko wrote:
>>> +static int alloc_int_buffers(struct xen_snd_front_shbuf *buf,
>>> + int num_pages_dir, int num_pages_buffer,
>>> + int num_grefs)
>>> +{
>>> + buf->grefs = kcalloc(num_grefs, sizeof(*buf->grefs), GFP_KERNEL);
>>> + if (!buf->grefs)
>>> + return -ENOMEM;
>>> +
>>> + buf->directory = kcalloc(num_pages_dir, XEN_PAGE_SIZE, GFP_KERNEL);
>>> + if (!buf->directory)
>>> + goto fail;
>>> +
>>> + buf->buffer_sz = num_pages_buffer * XEN_PAGE_SIZE;
>>> + buf->buffer = alloc_pages_exact(buf->buffer_sz, GFP_KERNEL);
>>> + if (!buf->buffer)
>>> + goto fail;
>>> +
>>> + return 0;
>>> +
>>> +fail:
>>> + kfree(buf->grefs);
>>> + buf->grefs = NULL;
>>> + kfree(buf->directory);
>> Why do you need to free those here? Shouldn't that be done via
>> xen_snd_front_shbuf_free() in case of an error?
> At this place we only allocate memory, but xen_snd_front_shbuf_free
> will also try to gnttab_end_foreign_access if buf->grefs != NULL.
Okay.
Juergen
next prev parent reply other threads:[~2018-04-17 11:15 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
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 [this message]
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=7abbbaa0-93c7-5c93-d653-ed5a04199f6e@suse.com \
--to=jgross@suse.com \
--cc=alsa-devel@alsa-project.org \
--cc=andr2000@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®