History

drm/i915: expose command stream timestamp frequency to userspace

We use to have this fixed per generation, but starting with CNL userspace cannot tell just off the PCI ID. Let's make this information available. This is particularly useful for performance monitoring where much of the normalization work is done using those timestamps (this include pipeline statistics in both GL & Vulkan as well as OA reports). v2: Use variables for 24MHz/19.2MHz values (Ewelina) Renamed function & coding style (Sagar) v3: Fix frequency read on Broadwell (Sagar) Fix missing divide by 4 on <= gen4 (Sagar)

Lionel Landwerlin committed 9 years ago

Commit dab91781 parent 95690a06 files · +141 −0Browse files

Showing the changes to include/uapi (1 of 6 files). Show all

Unified · Split

include/uapi/drm/i915_drm.h+6−0
@@ -481,6 +481,12 @@ typedef struct drm_i915_irq_wait { · 480 unmodified lines
481 */481 */
482#define I915_PARAM_HAS_CONTEXT_ISOLATION 50482#define I915_PARAM_HAS_CONTEXT_ISOLATION 50
483 483
484/* Frequency of the command streamer timestamps given by the *_TIMESTAMP
485 * registers. This used to be fixed per platform but from CNL onwards, this
486 * might vary depending on the parts.
487 */
488#define I915_PARAM_CS_TIMESTAMP_FREQUENCY 51
489
484typedef struct drm_i915_getparam {490typedef struct drm_i915_getparam {
485 __s32 param;491 __s32 param;
486 /*492 /*

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t