From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: John Hubbard <jhubbard@nvidia.com>, Shuah Khan <shuah@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Valentin Obst <kernel@valentinobst.de>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH v2] selftests/resctrl: fix clang build warnings related to abs(), labs() calls
Date: Wed, 8 May 2024 11:00:15 +0300 (EEST) [thread overview]
Message-ID: <7d4d8a31-00db-c7ba-aa8f-0483c8d93700@linux.intel.com> (raw)
In-Reply-To: <076d9990-6253-438d-bc92-70eba6dfbca9@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]
On Tue, 7 May 2024, Reinette Chatre wrote:
> Hi John,
>
> On 5/7/2024 6:25 PM, John Hubbard wrote:
> > On 5/7/24 6:21 PM, Reinette Chatre wrote:
> >> Hi John,
> > ...
> >>
> >> The following (what was in v1) looks good to me. What am I missing?
> >>
> >> diff --git a/tools/testing/selftests/resctrl/cmt_test.c b/tools/testing/selftests/resctrl/cmt_test.c
> >> index a81f91222a89..05a241519ae8 100644
> >> --- a/tools/testing/selftests/resctrl/cmt_test.c
> >> +++ b/tools/testing/selftests/resctrl/cmt_test.c
> >> @@ -40,11 +40,11 @@ static int show_results_info(unsigned long sum_llc_val, int no_of_bits,
> >> int ret;
> >> avg_llc_val = sum_llc_val / num_of_runs;
> >> - avg_diff = (long)abs(cache_span - avg_llc_val);
> >> + avg_diff = (long)(cache_span - avg_llc_val);
> >
> > This deletes the abs() call, because I incorrectly let clang's warning
> > lead me to believe that the abs() call was a no-op. But both you and Ilpo
> > pointed out that the math breaks if you do that.
>
> To me the extra abs() was unnecessary anyway ...
>
> >
> >> diff_percent = ((float)cache_span - avg_llc_val) / cache_span * 100;
> >> ret = platform && abs((int)diff_percent) > max_diff_percent &&
> >> - abs(avg_diff) > max_diff;
> >> + labs(avg_diff) > max_diff;
> >
>
> .. because it is repeated here.
Yes, there are two *abs() calls in this function.
In this case is okay to remove the first one since it didn't remove
absolute value completely, whereas in the MBA/MBM cases v1 removed *abs()
call entirely which was wrong thing to do.
I explicitly noted in my v1 comment that this CMT change is okay but the
other two were not.
--
i.
next prev parent reply other threads:[~2024-05-08 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 23:40 [PATCH v2] selftests/resctrl: fix clang build warnings related to abs(), labs() calls John Hubbard
2024-05-07 22:30 ` Reinette Chatre
2024-05-08 1:16 ` John Hubbard
2024-05-08 1:21 ` Reinette Chatre
2024-05-08 1:25 ` John Hubbard
2024-05-08 1:37 ` Reinette Chatre
2024-05-08 8:00 ` Ilpo Järvinen [this message]
2024-05-08 17:29 ` John Hubbard
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=7d4d8a31-00db-c7ba-aa8f-0483c8d93700@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=jhubbard@nvidia.com \
--cc=justinstitt@google.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=reinette.chatre@intel.com \
--cc=shuah@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