public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Lawrynowicz, Jacek" <jacek.lawrynowicz@intel.com>,
	Ben Widawsky <ben@bwidawsk.net>, Daniel Vetter <daniel@ffwll.ch>,
	"Jesse Barnes (jbarnes@virtuousgeek.org)"
	<jbarnes@virtuousgeek.org>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: TIMESTAMP register
Date: Wed, 18 Apr 2012 09:05:43 +0100	[thread overview]
Message-ID: <1334736361_17281@CP5-2952> (raw)
In-Reply-To: <36D38C1F74839847A52A484C31F3E51A154A1D9F@IRSMSX101.ger.corp.intel.com>

On Wed, 18 Apr 2012 07:53:36 +0000, "Lawrynowicz, Jacek" <jacek.lawrynowicz@intel.com> wrote:
> But how would I synchronize GPU and CPU clocks without access to the TIMESTAMP 
> register?
Issue a pipecontrol, compensate for the execution latency.

> And are you sure that over time both clocks won't desynchronize?
Given the assurrances made in the bspec, I'm certain the timestamp
will prove to be bogus and drift.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-04-18  8:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 19:12 TIMESTAMP register Lawrynowicz, Jacek
2012-04-17 19:39 ` Daniel Vetter
2012-04-17 20:34   ` Lawrynowicz, Jacek
2012-04-17 21:04     ` Daniel Vetter
2012-04-17 23:27       ` Ben Widawsky
2012-04-17 23:51         ` Chris Wilson
2012-04-18  6:32           ` Lawrynowicz, Jacek
2012-04-18  7:35             ` Chris Wilson
2012-04-18  7:53               ` Lawrynowicz, Jacek
2012-04-18  8:05                 ` Chris Wilson [this message]
2012-04-30 21:11           ` Eric Anholt

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=1334736361_17281@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=ben@bwidawsk.net \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jacek.lawrynowicz@intel.com \
    --cc=jbarnes@virtuousgeek.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