aboutsummaryrefslogtreecommitdiffstats
path: root/src/gallium/drivers/iris/iris_monitor.c
Commit message (Collapse)AuthorAgeFilesLines
* intel/perf: move query_mask and location out of gen_perf_query_counterMarcin Ślusarz2020-07-061-5/+6
| | | | | | | Signed-off-by: Marcin Ślusarz <[email protected]> Reviewed-by: Lionel Landwerlin <[email protected]> Reviewed-by: Mark Janes <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5399>
* iris: remove iris_monitor_configMarcin Ślusarz2020-07-061-93/+19
| | | | | | | | | | | | | | | | | | | perf_cfg is enough - it already contains almost all necessary information and is constructed in a more optimal way (O(n) vs O(n^2) - it uses hash table to build the unique counter list). "Almost all", because it doesn't contain OA raw counters, but we should have not exposed them anyway. Quoting Mark Janes: "I see no reason to include the OA raw counters in the list that are provided to the user. They are unusable. The MDAPI library can be used to configure raw counters in a way that provides esoteric metrics, but that library is written against INTEL_performance_query." Signed-off-by: Marcin Ślusarz <[email protected]> Reviewed-by: Lionel Landwerlin <[email protected]> Reviewed-by: Mark Janes <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5399>
* iris: return max counter value for AMD_performance_monitorMarcin Ślusarz2020-07-061-3/+4
| | | | | | | | | | | | glGetPerfMonitorCounterInfoAMD(..., ..., GL_COUNTER_RANGE_AMD, ...) returned NAN (binary representation of uint64_t(-1) as float) as a max value. Fixes: 0fd4359733e6 ("iris/perf: implement routines to return counter info") Signed-off-by: Marcin Ślusarz <[email protected]> Reviewed-by: Lionel Landwerlin <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5473>
* intel/perf: make pipeline statistic query loading optionalLionel Landwerlin2020-05-201-1/+2
| | | | | | | | | On Vulkan most of those are already covered by standard queries so add the ability to skip them. Signed-off-by: Lionel Landwerlin <[email protected]> Reviewed-by: Jason Ekstrand <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2775>
* iris: separating out common perf codeMark Janes2019-12-101-92/+2
| | | | | | | | | | The configuration of the gen_perf vtable will be the same for INTEL_performance_query and AMD_performance_monitor. Initialize the table in a single routine that can be called from both implementations. Signed-off-by: Dongwon Kim <[email protected]> Reviewed-by: Kenneth Graunke <[email protected]>
* intel/perf: move registers to their own headerLionel Landwerlin2019-10-231-0/+1
| | | | | | | Will conflict with the genxml RPSTAT register. Signed-off-by: Lionel Landwerlin <[email protected]> Reviewed-by: Rafael Antognolli <[email protected]>
* iris: Add missing 'break'Kenneth Graunke2019-08-111-0/+1
| | | | | | We don't want to fall through to unreachable(). CID: 1452277
* iris: minor restylingKenneth Graunke2019-08-101-34/+42
|
* iris/perf: get monitor resultsMark Janes2019-08-091-0/+60
| | | | Reviewed-by: Kenneth Graunke <[email protected]>
* iris/perf: add begin/end hooksMark Janes2019-08-091-0/+21
| | | | Reviewed-by: Kenneth Graunke <[email protected]>
* iris/perf: add delete queryMark Janes2019-08-091-0/+12
| | | | Reviewed-by: Kenneth Graunke <[email protected]>
* iris/perf: implement iris_create_monitor_objectMark Janes2019-08-091-0/+99
| | | | | | | | This is the first call that provides the iris context to the monitor implementation. On the first call, use the iris context to initialize the monitor context. Reviewed-by: Kenneth Graunke <[email protected]>
* iris/perf: implement routines to return counter infoMark Janes2019-08-091-0/+281
With this commit, Iris will report that AMD_performance_monitor is supported, and will allow the caller to query the available metrics. Reviewed-by: Kenneth Graunke <[email protected]>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-14 15:55:19 +0000