From 1aa163ebb5b90dc0fdf224f7a14c2ff88093c2aa Mon Sep 17 00:00:00 2001 From: Emma Anholt Date: Thu, 5 Jan 2023 13:34:25 -0800 Subject: [PATCH] anv: Print the BO sizes in KB instead of hex bytes. We already show the address range, which is most of why I'd think you'd be looking at hex values. I find a more human-readable number nice for debugging, instead of counting zeroes to decide if it's 1.5MB or 96kb. Reviewed-by: Lionel Landwerlin Part-of: --- src/intel/vulkan/anv_batch_chain.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/intel/vulkan/anv_batch_chain.c b/src/intel/vulkan/anv_batch_chain.c index e4260327e4e..c9eba21c8cd 100644 --- a/src/intel/vulkan/anv_batch_chain.c +++ b/src/intel/vulkan/anv_batch_chain.c @@ -1842,9 +1842,9 @@ anv_queue_exec_locked(struct anv_queue *queue, const struct anv_bo *bo = execbuf.bos[i]; uint64_t size = bo->size + bo->_ccs_size; - fprintf(stderr, " BO: addr=0x%016"PRIx64"-0x%016"PRIx64" size=0x%010"PRIx64 - " handle=%05u capture=%u name=%s\n", - bo->offset, bo->offset + size - 1, size, bo->gem_handle, + fprintf(stderr, " BO: addr=0x%016"PRIx64"-0x%016"PRIx64" size=%7"PRIu64 + "KB handle=%05u capture=%u name=%s\n", + bo->offset, bo->offset + size - 1, size / 1024, bo->gem_handle, (bo->flags & EXEC_OBJECT_CAPTURE) != 0, bo->name); } }