From: Lars-Peter Clausen <lars@metafoo.de>
To: Jiada Wang <jiada_wang@mentor.com>, perex@perex.cz, tiwai@suse.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
apape@de.adit-jv.com
Subject: Re: [PATCH 1/1] ALSA: SOC: DMA: increment buffer pointer atomically
Date: Wed, 30 Nov 2016 09:36:16 +0100 [thread overview]
Message-ID: <ef0cef5f-4f79-919c-c040-5d67b9280977@metafoo.de> (raw)
In-Reply-To: <36d5025d-d327-878d-7f2e-5bf0c457581d@metafoo.de>
On 11/30/2016 09:30 AM, Lars-Peter Clausen wrote:
> On 11/30/2016 09:22 AM, Jiada Wang wrote:
>> From: Andreas Pape <apape@de.adit-jv.com>
>>
>> Setting pointer and afterwards check for wrap around leads
>> to the possibility of returning the inconsistent pointer position.
>> This patch increments buffer pointer atomically to avoid this issue.
>
> Makes sense.
>
>>
>> Signed-off-by: Andreas Pape <apape@de.adit-jv.com>
>> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
>> ---
>> sound/core/pcm_dmaengine.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/sound/core/pcm_dmaengine.c b/sound/core/pcm_dmaengine.c
>> index 8eb58c7..6f6da11 100644
>> --- a/sound/core/pcm_dmaengine.c
>> +++ b/sound/core/pcm_dmaengine.c
>> @@ -139,12 +139,14 @@ EXPORT_SYMBOL_GPL(snd_dmaengine_pcm_set_config_from_dai_data);
>>
>> static void dmaengine_pcm_dma_complete(void *arg)
>> {
>> + unsigned int new_pos;
>> struct snd_pcm_substream *substream = arg;
>> struct dmaengine_pcm_runtime_data *prtd = substream_to_prtd(substream);
>>
>> - prtd->pos += snd_pcm_lib_period_bytes(substream);
>> - if (prtd->pos >= snd_pcm_lib_buffer_bytes(substream))
>> - prtd->pos = 0;
>> + new_pos = prtd->pos + snd_pcm_lib_period_bytes(substream);
>> + if (new_pos >= snd_pcm_lib_buffer_bytes(substream))
>> + new_pos = 0;
>> + prtd->pos = new_pos;
>
> But to really make it atomic I think this needs READ_ONCE/WRITE_ONCE.
And the access to prtd->pos in snd_dmaengine_pcm_pointer_no_residue() should
also use READ_ONCE(). It is very unlikely that the code gets mis-compiled to
generate more than one access, but having READ_ONCE() acts as a annotation
that makes it explicit that this is data that can be updated concurrently
without further synchronization.
next prev parent reply other threads:[~2016-11-30 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 8:22 Jiada Wang
2016-11-30 8:30 ` Lars-Peter Clausen
2016-11-30 8:36 ` Lars-Peter Clausen [this message]
2016-11-30 9:16 ` Lars-Peter Clausen
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=ef0cef5f-4f79-919c-c040-5d67b9280977@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=apape@de.adit-jv.com \
--cc=jiada_wang@mentor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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®