From: Peter Hurley <peter@hurleysoftware.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Michel Dänzer" <michel@daenzer.net>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/vblank: Fixup and document timestamp update/read barriers
Date: Tue, 05 May 2015 15:01:20 -0400 [thread overview]
Message-ID: <55491380.1@hurleysoftware.com> (raw)
In-Reply-To: <5548E876.4010706@hurleysoftware.com>
On 05/05/2015 11:57 AM, Peter Hurley wrote:
> On 05/05/2015 11:42 AM, Daniel Vetter wrote:
>> I'm also somewhat confused about how you to a line across both cpus for
>> barriers because barriers only have cpu-local effects (which is why we
>> always need a barrier on both ends of a transaction).
I'm sorry if my barrier notation confuses you; I find that it clearly
identifies matching pairs.
Also, there is a distinction between "can be visible" and "must be visible";
the load and stores themselves are not cpu-local.
Regards,
Peter Hurley
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-05 19:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 7:17 [PATCH] drm/vblank: Fixup and document timestamp update/read barriers Daniel Vetter
2015-04-15 8:17 ` Chris Wilson
2015-04-15 9:25 ` Daniel Vetter
2015-04-15 9:36 ` Chris Wilson
2015-04-15 10:32 ` Daniel Vetter
2015-04-15 17:34 ` Daniel Vetter
2015-04-15 17:49 ` Chris Wilson
2015-04-15 21:26 ` Mario Kleiner
2015-04-16 1:29 ` Peter Hurley
2015-04-16 6:39 ` Mario Kleiner
2015-04-16 9:00 ` Peter Hurley
2015-04-16 9:06 ` Daniel Vetter
2015-04-16 12:52 ` Peter Hurley
2015-04-16 8:54 ` Daniel Vetter
2015-04-16 0:17 ` shuang.he
2015-04-16 8:59 ` Daniel Vetter
2015-04-17 4:27 ` shuang.he
2015-04-16 0:18 ` shuang.he
2015-04-15 13:00 ` Peter Hurley
2015-04-15 17:31 ` Daniel Vetter
2015-04-16 12:30 ` Peter Hurley
2015-04-16 13:03 ` [Intel-gfx] " Daniel Vetter
2015-05-04 4:52 ` Mario Kleiner
2015-05-05 14:36 ` Peter Hurley
2015-05-05 15:42 ` [Intel-gfx] " Daniel Vetter
2015-05-05 15:57 ` Peter Hurley
2015-05-05 19:01 ` Peter Hurley [this message]
2015-05-06 8:56 ` Daniel Vetter
2015-05-07 11:56 ` [Intel-gfx] " Peter Hurley
2015-05-07 17:33 ` Mario Kleiner
2015-04-15 19:40 ` shuang.he
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=55491380.1@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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