public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Shivank Garg <shivankg@amd.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, <acme@redhat.com>,
	<namhyung@kernel.org>, <leo.yan@arm.com>,
	<yangyicong@hisilicon.com>, <bp@alien8.de>, <mingo@kernel.org>,
	<xin@zytor.com>, <yosry.ahmed@linux.dev>, <shivankg@amd.com>,
	<oliver.sang@intel.com>
Subject: Re: [PATCH] tools headers: Sync x86 cpufeatures and arm64 cputype headers
Date: Thu, 2 Oct 2025 16:02:10 +0800	[thread overview]
Message-ID: <202510021503.f668f456-lkp@intel.com> (raw)
In-Reply-To: <20250929061644.19188-2-shivankg@amd.com>



Hello,

kernel test robot noticed "perf-sanity-tests.perf.make.fail" on:

commit: 00bacc579a0558c23b9fb50846091d3eb69dcd12 ("[PATCH] tools headers: Sync x86 cpufeatures and arm64 cputype headers")
url: https://github.com/intel-lab-lkp/linux/commits/Shivank-Garg/tools-headers-Sync-x86-cpufeatures-and-arm64-cputype-headers/20250929-141957
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a
patch link: https://lore.kernel.org/all/20250929061644.19188-2-shivankg@amd.com/
patch subject: [PATCH] tools headers: Sync x86 cpufeatures and arm64 cputype headers

in testcase: perf-sanity-tests
version: 
with following parameters:

	perf_compiler: clang
	group: group-01



config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 224 threads 4 sockets Intel(R) Xeon(R) Platinum 8380H CPU @ 2.90GHz (Cooper Lake) with 192G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)



If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202510021503.f668f456-lkp@intel.com


user  :err   : [  247.978055] [   T2565] util/arm-spe.c: In function ‘arm_spe__synth_ds’:

user  :err   : [  248.467637] [   T2565] util/arm-spe.c:885:43: error: passing argument 1 of ‘is_midr_in_range_list’ makes pointer from integer without a cast [-Wint-conversion]

user  :err   : [  248.495319] [   T2565]   885 |                 if (is_midr_in_range_list(midr, data_source_handles[i].midr_ranges)) {

user  :err   : [  248.512094] [   T2565]       |                                           ^~~~

user  :err   : [  248.526499] [   T2565]       |                                           |

user  :err   : [  248.542706] [   T2565]       |                                           u64 {aka long unsigned int}

user  :err   : [  248.558780] [   T2565] In file included from util/arm-spe.c:37:

user  :err   : [  249.826660] [   T2565] util/../../arch/arm64/include/asm/cputype.h:306:53: note: expected ‘const struct midr_range *’ but argument is of type ‘u64’ {aka ‘long unsigned int’}

user  :err   : [  249.854297] [   T2565]   306 | bool is_midr_in_range_list(struct midr_range const *ranges);

user  :err   : [  249.871522] [   T2565]       |                            ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~

user  :err   : [  250.353462] [   T2565] util/arm-spe.c:885:21: error: too many arguments to function ‘is_midr_in_range_list’

user  :err   : [  250.373933] [   T2565]   885 |                 if (is_midr_in_range_list(midr, data_source_handles[i].midr_ranges)) {

user  :err   : [  250.392421] [   T2565]       |                     ^~~~~~~~~~~~~~~~~~~~~

user  :err   : [  250.408497] [   T2565] util/../../arch/arm64/include/asm/cputype.h:306:6: note: declared here

user  :err   : [  250.422856] [   T2565]   306 | bool is_midr_in_range_list(struct midr_range const *ranges);

user  :err   : [  250.439238] [   T2565]       |      ^~~~~~~~~~~~~~~~~~~~~

user  :err   : [  250.465872] [   T2565] make[4]: *** [/usr/src/perf_selftests-x86_64-rhel-9.4-bpf-00bacc579a0558c23b9fb50846091d3eb69dcd12/tools/build/Makefile.build:85: util/arm-spe.o] Error 1

user  :err   : [  250.488993] [   T2565] make[4]: *** Waiting for unfinished jobs....

user  :err   : [  250.502580] [   T2565] make[3]: *** [/usr/src/perf_selftests-x86_64-rhel-9.4-bpf-00bacc579a0558c23b9fb50846091d3eb69dcd12/tools/build/Makefile.build:142: util] Error 2

user  :err   : [  250.527554] [   T2565] make[2]: *** [Makefile.perf:797: perf-util-in.o] Error 2



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251002/202510021503.f668f456-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


      parent reply	other threads:[~2025-10-02  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29  6:16 [PATCH] tools headers: Sync x86 cpufeatures and arm64 cputype headers Shivank Garg
2025-09-29  8:27 ` Leo Yan
2025-09-29  9:17   ` Garg, Shivank
2025-09-30  6:40     ` Garg, Shivank
2025-10-02  8:02 ` kernel test robot [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=202510021503.f668f456-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=acme@redhat.com \
    --cc=bp@alien8.de \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=shivankg@amd.com \
    --cc=xin@zytor.com \
    --cc=yangyicong@hisilicon.com \
    --cc=yosry.ahmed@linux.dev \
    /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