mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	namhyung@kernel.org, irogers@google.com
Subject: Re: [PATCH] perf hist: Fix width calculation in hpp__fmt()
Date: Wed, 8 Jan 2025 17:41:55 +0000	[thread overview]
Message-ID: <c2d6551a-2345-4d6c-a0ec-06096a4d3a21@linaro.org> (raw)
In-Reply-To: <dc6b9a84-75d7-483d-87e5-3f5d76858d67@linaro.org>



On 08/01/2025 5:26 pm, James Clark wrote:
> 
> 
> On 08/01/2025 6:59 am, Dmitry Vyukov wrote:
>> hpp__width_fn() round up width to length of the field name,
>> hpp__fmt() should do it too. Otherwise, the numbers may
>> end up unaligned if the field name is long.
>>
>> Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
>> Cc: Namhyung Kim <namhyung@kernel.org>
>> Cc: Ian Rogers <irogers@google.com>
>> Cc: linux-perf-users@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> ---
>>   tools/perf/ui/hist.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/ui/hist.c b/tools/perf/ui/hist.c
>> index e5491995adf08..34fda1d5eccb4 100644
>> --- a/tools/perf/ui/hist.c
>> +++ b/tools/perf/ui/hist.c
>> @@ -121,7 +121,7 @@ int hpp__fmt(struct perf_hpp_fmt *fmt, struct 
>> perf_hpp *hpp,
>>            const char *fmtstr, hpp_snprint_fn print_fn,
>>            enum perf_hpp_fmt_type fmtype)
>>   {
>> -    int len = fmt->user_len ?: fmt->len;
>> +    int len = max(fmt->user_len ?: fmt->len, (int)strlen(fmt->name));
>>       if (symbol_conf.field_sep) {
>>           return __hpp__fmt(hpp, he, get_field, fmtstr, 1,
>>
>> base-commit: 09a0fa92e5b45e99cf435b2fbf5ebcf889cf8780
> 
> This seems to right align the field correctly with a long name. Although 
> it's worth noting I had to add a long name to make it obvious.
> 
> Reviewed-by: James Clark <james.clark@linaro.org>
> 
> I saw some other existing issue with small column-width arguments which 
> is changed slightly by this patch. But I don't think it's worse:
> 

Ah maybe I was looking at it wrong, before and after are the same with 
width=3, apart from the intended fix. False alarm.

> 
> $ perf report --fields 
> overhead,overhead_sys,overhead_us,overhead_guest_us,dso --column- 
> widths=3,3,3,3,3
> 
> After:
> ------
> Overhead       sys       usr  guest usr long name  Shared Object
>    63.78%     0.00%    63.78%                0.00%  ld-linux-x86-64.so
> 
> After, width=3:
> --------------
> Overhead       sys       usr  guest usr long name  Sha
>    63.78%   0.00%     63.78%                 0.00%  ld-
> 
> Before:
> ---------------
> Overhead       sys       usr  guest usr long name  Shared Object
>    63.78%     0.00%    63.78%      0.00%            ld-linux-x86-64.so
> 
> Before, width=3:
> ---------------
> Overhead       sys       usr  guest usr long name  Sha
>   63.78%    0.00%     63.78%    0.00%               ld-


  reply	other threads:[~2025-01-08 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08  6:59 Dmitry Vyukov
2025-01-08 17:26 ` James Clark
2025-01-08 17:41   ` James Clark [this message]
2025-01-17 17:54 ` Namhyung Kim

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=c2d6551a-2345-4d6c-a0ec-06096a4d3a21@linaro.org \
    --to=james.clark@linaro.org \
    --cc=dvyukov@google.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.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

all inboxes | Powered by JetHome®