From: kernel test robot <lkp@intel.com>
To: Rajnesh Kanwal <rkanwal@rivosinc.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Atish Kumar Patra <atishp@rivosinc.com>,
Anup Patel <anup@brainfault.org>, Will Deacon <will@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Beeman Strong <beeman@rivosinc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Rajnesh Kanwal <rkanwal@rivosinc.com>
Subject: Re: [PATCH v3 5/7] riscv: pmu: Add driver for Control Transfer Records Ext.
Date: Sat, 24 May 2025 01:48:04 +0800 [thread overview]
Message-ID: <202505240131.OJkUGGvA-lkp@intel.com> (raw)
In-Reply-To: <20250523-b4-ctr_upstream_v3-v3-5-ad355304ba1c@rivosinc.com>
Hi Rajnesh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on e0200e37637e573cd68f522ecd550be87e304c6c]
url: https://github.com/intel-lab-lkp/linux/commits/Rajnesh-Kanwal/perf-Increase-the-maximum-number-of-branches-remove_loops-can-process/20250523-073341
base: e0200e37637e573cd68f522ecd550be87e304c6c
patch link: https://lore.kernel.org/r/20250523-b4-ctr_upstream_v3-v3-5-ad355304ba1c%40rivosinc.com
patch subject: [PATCH v3 5/7] riscv: pmu: Add driver for Control Transfer Records Ext.
config: riscv-randconfig-002-20250523 (https://download.01.org/0day-ci/archive/20250524/202505240131.OJkUGGvA-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250524/202505240131.OJkUGGvA-lkp@intel.com/reproduce)
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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505240131.OJkUGGvA-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/riscv/kernel/asm-offsets.c:12:
In file included from arch/riscv/include/asm/kvm_host.h:23:
In file included from arch/riscv/include/asm/kvm_vcpu_pmu.h:12:
>> include/linux/perf/riscv_pmu.h:156:76: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
156 | static inline void riscv_pmu_ctr_sched_task(struct perf_event_pmu_context *,
| ^
include/linux/perf/riscv_pmu.h:158:13: warning: unused function 'riscv_pmu_ctr_add' [-Wunused-function]
158 | static void riscv_pmu_ctr_add(struct perf_event *event) { }
| ^~~~~~~~~~~~~~~~~
include/linux/perf/riscv_pmu.h:159:13: warning: unused function 'riscv_pmu_ctr_del' [-Wunused-function]
159 | static void riscv_pmu_ctr_del(struct perf_event *event) { }
| ^~~~~~~~~~~~~~~~~
3 warnings generated.
--
In file included from arch/riscv/kernel/asm-offsets.c:12:
In file included from arch/riscv/include/asm/kvm_host.h:23:
In file included from arch/riscv/include/asm/kvm_vcpu_pmu.h:12:
>> include/linux/perf/riscv_pmu.h:156:76: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
156 | static inline void riscv_pmu_ctr_sched_task(struct perf_event_pmu_context *,
| ^
include/linux/perf/riscv_pmu.h:158:13: warning: unused function 'riscv_pmu_ctr_add' [-Wunused-function]
158 | static void riscv_pmu_ctr_add(struct perf_event *event) { }
| ^~~~~~~~~~~~~~~~~
include/linux/perf/riscv_pmu.h:159:13: warning: unused function 'riscv_pmu_ctr_del' [-Wunused-function]
159 | static void riscv_pmu_ctr_del(struct perf_event *event) { }
| ^~~~~~~~~~~~~~~~~
3 warnings generated.
vim +156 include/linux/perf/riscv_pmu.h
152
153 static inline bool riscv_pmu_ctr_valid(struct perf_event *event) { return false; }
154 static inline void riscv_pmu_ctr_consume(struct cpu_hw_events *cpuc,
155 struct perf_event *event) { }
> 156 static inline void riscv_pmu_ctr_sched_task(struct perf_event_pmu_context *,
157 bool sched_in) { }
158 static void riscv_pmu_ctr_add(struct perf_event *event) { }
159 static void riscv_pmu_ctr_del(struct perf_event *event) { }
160 static inline void riscv_pmu_ctr_enable(struct perf_event *event) { }
161 static inline void riscv_pmu_ctr_disable(struct perf_event *event) { }
162 static inline void riscv_pmu_ctr_dying_cpu(void) { }
163 static inline void riscv_pmu_ctr_starting_cpu(void) { }
164 static inline int riscv_pmu_ctr_init(struct riscv_pmu *riscv_pmu) { return 0; }
165 static inline void riscv_pmu_ctr_finish(struct riscv_pmu *riscv_pmu) { }
166
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-05-23 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 23:25 [PATCH v3 0/7] riscv: pmu: Add support for Control Transfer Records Ext Rajnesh Kanwal
2025-05-22 23:25 ` [PATCH v3 1/7] perf: Increase the maximum number of branches remove_loops() can process Rajnesh Kanwal
2025-05-27 9:59 ` Rajnesh Kanwal
2025-05-22 23:25 ` [PATCH v3 2/7] riscv: pmu: Add Control transfer records CSR definations Rajnesh Kanwal
2025-05-22 23:25 ` [PATCH v3 3/7] riscv: Add Control Transfer Records extension parsing Rajnesh Kanwal
2025-05-22 23:25 ` [PATCH v3 4/7] riscv: pmu: Add infrastructure for Control Transfer Record Rajnesh Kanwal
2025-05-22 23:25 ` [PATCH v3 5/7] riscv: pmu: Add driver for Control Transfer Records Ext Rajnesh Kanwal
2025-05-23 17:48 ` kernel test robot [this message]
2025-05-22 23:25 ` [PATCH v3 6/7] riscv: pmu: Integrate CTR Ext support in riscv_pmu_dev driver Rajnesh Kanwal
2025-05-22 23:25 ` [PATCH v3 7/7] dt-bindings: riscv: add Sxctr ISA extension description Rajnesh Kanwal
2025-05-23 15:36 ` Conor Dooley
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=202505240131.OJkUGGvA-lkp@intel.com \
--to=lkp@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alex@ghiti.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=beeman@rivosinc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=rkanwal@rivosinc.com \
--cc=robh@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).