From: Daniel Vetter <daniel@ffwll.ch>
To: "Lawrynowicz, Jacek" <jacek.lawrynowicz@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: TIMESTAMP register
Date: Tue, 17 Apr 2012 21:39:43 +0200 [thread overview]
Message-ID: <20120417193943.GR4104@phenom.ffwll.local> (raw)
In-Reply-To: <36D38C1F74839847A52A484C31F3E51A154A0E59@IRSMSX101.ger.corp.intel.com>
On Tue, Apr 17, 2012 at 07:12:40PM +0000, Lawrynowicz, Jacek wrote:
> Starting from IVB the main TIMESTAMP register is longer than 32 bits
> (it’s 36 bits long).
>
> How should we pass its 36 bit value from i915 to user space?
>
> GET_PARAM ioctls supports only 32 bit params. Should we add GET_PARAM64
> or create separate ioctl to access the TIMESTAMP?
>
> Any suggestions?
>
>
>
> This functionality is required for any OpenGL driver which implements GL_ARB_timer_query.
Like occlusion queries I presume this should be done with a pipe control
qword write issued from a batch. GETPARAM makes absolutely no sense, that
is for driver features, not hw features and just used so that a new driver
also can work on an older kernel.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-04-17 19:38 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 [this message]
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
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=20120417193943.GR4104@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jacek.lawrynowicz@intel.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