From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: igt-dev@lists.freedesktop.org, Intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH i-g-t 2/2] intel_gpu_top: Use full console width for global metrics
Date: Thu, 16 Mar 2023 10:06:49 +0000 [thread overview]
Message-ID: <20230316100649.1261221-2-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20230316100649.1261221-1-tvrtko.ursulin@linux.intel.com>
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
It appears we had an off by one of a kind where we were not using the full
width of the terminal window for the global metrics section.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
tools/intel_gpu_top.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c
index 39be916297e4..36da016c3df0 100644
--- a/tools/intel_gpu_top.c
+++ b/tools/intel_gpu_top.c
@@ -1960,8 +1960,7 @@ print_engines_header(struct engines *engines, double t,
a = " ENGINE BUSY ";
printf("\033[7m%s%*s%s\033[0m\n",
- a, (int)(con_w - 1 - strlen(a) - strlen(b)),
- " ", b);
+ a, (int)(con_w - strlen(a) - strlen(b)), " ", b);
lines++;
}
@@ -2000,7 +1999,6 @@ print_engine(struct engines *engines, unsigned int i, double t,
print_groups(groups);
if (output_mode == INTERACTIVE) {
- unsigned int max_w = con_w - 1;
unsigned int len;
char buf[128];
double val;
@@ -2012,7 +2010,7 @@ print_engine(struct engines *engines, unsigned int i, double t,
engine->display_name, engine_items[0].buf);
val = pmu_calc(&engine->busy.val, 1e9, t, 100);
- print_percentage_bar(val, max_w > len ? max_w - len : 0, false);
+ print_percentage_bar(val, con_w > len ? con_w - len : 0, false);
printf("%s\n", buf);
--
2.37.2
prev parent reply other threads:[~2023-03-16 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 10:06 [Intel-gfx] [PATCH i-g-t 1/2] intel_gpu_top: Display large pids nicely in interactive mode Tvrtko Ursulin
2023-03-16 10:06 ` Tvrtko Ursulin [this message]
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=20230316100649.1261221-2-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
/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