linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	freedreno <freedreno@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/msm: use proper memory barriers for updating tail/head
Date: Tue, 3 Oct 2017 08:59:47 -0400	[thread overview]
Message-ID: <CAF6AEGtqbWKbDidWiBksx2L3OwonzSe4eSYmvJB4xV22Fm4HFg@mail.gmail.com> (raw)
In-Reply-To: <20171003080812.xdzymkuloam3d2cj@phenom.ffwll.local>

On Tue, Oct 3, 2017 at 4:08 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, Oct 02, 2017 at 10:37:11AM -0400, Rob Clark wrote:
>> Fixes intermittent corruption of cmdstream dump.
>>
>> Signed-off-by: Rob Clark <robdclark@gmail.com>
>
> Rule of memory barriers: They always need to come in pairs, and you should
> put a comment to each one explaining where the other side is. I.e. for all
> the store_release ones you add here you need to put a few read_acquire
> ones somewhere else, and then explain how they link.
>
> One side only doesn't really work with barriers - except when you're lucky
> and on x86 :-)

fwiw, this is straight out of Documentation/circular-buffers.txt

I guess it could read_acquire when checking the avail/free space on
the consumer/producer side.. otoh if we see an old value there it is
harmless (ie. we just fall into a wait_event()).  I assume that is why
the documentation didn't bother with a read_acquire.

BR,
-R

> -Daniel
>> ---
>>  drivers/gpu/drm/msm/msm_rd.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/msm_rd.c b/drivers/gpu/drm/msm/msm_rd.c
>> index 5c087a4228ff..918c65e19964 100644
>> --- a/drivers/gpu/drm/msm/msm_rd.c
>> +++ b/drivers/gpu/drm/msm/msm_rd.c
>> @@ -120,7 +120,7 @@ static void rd_write(struct msm_rd_state *rd, const void *buf, int sz)
>>               n = min(sz, circ_space_to_end(&rd->fifo));
>>               memcpy(fptr, ptr, n);
>>
>> -             fifo->head = (fifo->head + n) & (BUF_SZ - 1);
>> +             smp_store_release(&fifo->head, (fifo->head + n) & (BUF_SZ - 1));
>>               sz  -= n;
>>               ptr += n;
>>
>> @@ -157,7 +157,7 @@ static ssize_t rd_read(struct file *file, char __user *buf,
>>               goto out;
>>       }
>>
>> -     fifo->tail = (fifo->tail + n) & (BUF_SZ - 1);
>> +     smp_store_release(&fifo->tail, (fifo->tail + n) & (BUF_SZ - 1));
>>       *ppos += n;
>>
>>       wake_up_all(&rd->fifo_event);
>> --
>> 2.13.5
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-10-03 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 14:37 [PATCH] drm/msm: use proper memory barriers for updating tail/head Rob Clark
2017-10-03  8:08 ` Daniel Vetter
2017-10-03 12:59   ` Rob Clark [this message]
2017-10-03 16:11     ` Daniel Vetter

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=CAF6AEGtqbWKbDidWiBksx2L3OwonzSe4eSYmvJB4xV22Fm4HFg@mail.gmail.com \
    --to=robdclark@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.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).