diff options
author | Nicolai Hähnle <[email protected]> | 2015-11-24 14:54:54 +0100 |
---|---|---|
committer | Nicolai Hähnle <[email protected]> | 2015-11-25 15:28:09 +0100 |
commit | b9fc01aee75dcc2d56750ea430e32d74127faf69 (patch) | |
tree | 86ee630ab135f1bd312a55e772c60eff1c2def65 | |
parent | 592928065cc606c5acfe0fc13ce71532bf5cf726 (diff) |
radeon: scale query buffer size to result size
Performance monitor queries can become very big, especially considering that
instances of a block in different shader engines are queried separately.
Reviewed-by: Marek Olšák <[email protected]>
-rw-r--r-- | src/gallium/drivers/radeon/r600_query.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gallium/drivers/radeon/r600_query.c b/src/gallium/drivers/radeon/r600_query.c index b1cfb6e462b..38bbbbf8a5e 100644 --- a/src/gallium/drivers/radeon/r600_query.c +++ b/src/gallium/drivers/radeon/r600_query.c @@ -232,7 +232,7 @@ void r600_query_hw_destroy(struct r600_common_context *rctx, static struct r600_resource *r600_new_query_buffer(struct r600_common_context *ctx, struct r600_query_hw *query) { - unsigned buf_size = 4096; + unsigned buf_size = MAX2(query->result_size, 4096); /* Queries are normally read by the CPU after * being written by the gpu, hence staging is probably a good |