From: kernel test robot <lkp@intel.com>
To: Gowthami Thiagarajan <gthiagarajan@marvell.com>,
will@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, sgoutham@marvell.com,
lcherian@marvell.com, gcherian@marvell.com,
Gowthami Thiagarajan <gthiagarajan@marvell.com>
Subject: Re: [PATCH v7] perf/marvell: Marvell PEM performance monitor support
Date: Fri, 20 Sep 2024 11:35:34 +0800 [thread overview]
Message-ID: <202409201101.hqshrCE7-lkp@intel.com> (raw)
In-Reply-To: <20240919125117.3484572-1-gthiagarajan@marvell.com>
Hi Gowthami,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/smp/core]
[also build test WARNING on soc/for-next linus/master v6.11 next-20240919]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Gowthami-Thiagarajan/perf-marvell-Marvell-PEM-performance-monitor-support/20240919-205406
base: tip/smp/core
patch link: https://lore.kernel.org/r/20240919125117.3484572-1-gthiagarajan%40marvell.com
patch subject: [PATCH v7] perf/marvell: Marvell PEM performance monitor support
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20240920/202409201101.hqshrCE7-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240920/202409201101.hqshrCE7-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/202409201101.hqshrCE7-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/perf/marvell_pem_pmu.c: In function 'pem_perf_read_counter':
drivers/perf/marvell_pem_pmu.c:232:16: error: implicit declaration of function 'readq_relaxed'; did you mean 'readl_relaxed'? [-Wimplicit-function-declaration]
232 | return readq_relaxed(pmu->base + eventid_to_offset(eventid));
| ^~~~~~~~~~~~~
| readl_relaxed
drivers/perf/marvell_pem_pmu.c: In function 'pem_perf_probe':
>> drivers/perf/marvell_pem_pmu.c:353:78: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'resource_size_t' {aka 'unsigned int'} [-Wformat=]
353 | name = devm_kasprintf(pem_pmu->dev, GFP_KERNEL, "mrvl_pcie_rc_pmu_%llx",
| ~~~^
| |
| long long unsigned int
| %x
354 | res->start);
| ~~~~~~~~~~
| |
| resource_size_t {aka unsigned int}
vim +353 drivers/perf/marvell_pem_pmu.c
315
316 static int pem_perf_probe(struct platform_device *pdev)
317 {
318 struct pem_pmu *pem_pmu;
319 struct resource *res;
320 void __iomem *base;
321 char *name;
322 int ret;
323
324 pem_pmu = devm_kzalloc(&pdev->dev, sizeof(*pem_pmu), GFP_KERNEL);
325 if (!pem_pmu)
326 return -ENOMEM;
327
328 pem_pmu->dev = &pdev->dev;
329 platform_set_drvdata(pdev, pem_pmu);
330
331 base = devm_platform_get_and_ioremap_resource(pdev, 0, &res);
332 if (IS_ERR(base))
333 return PTR_ERR(base);
334
335 pem_pmu->base = base;
336
337 pem_pmu->pmu = (struct pmu) {
338 .module = THIS_MODULE,
339 .capabilities = PERF_PMU_CAP_NO_EXCLUDE,
340 .task_ctx_nr = perf_invalid_context,
341 .attr_groups = pem_perf_attr_groups,
342 .event_init = pem_perf_event_init,
343 .add = pem_perf_event_add,
344 .del = pem_perf_event_del,
345 .start = pem_perf_event_start,
346 .stop = pem_perf_event_stop,
347 .read = pem_perf_event_update,
348 };
349
350 /* Choose this cpu to collect perf data */
351 pem_pmu->cpu = raw_smp_processor_id();
352
> 353 name = devm_kasprintf(pem_pmu->dev, GFP_KERNEL, "mrvl_pcie_rc_pmu_%llx",
354 res->start);
355 if (!name)
356 return -ENOMEM;
357
358 cpuhp_state_add_instance_nocalls(CPUHP_AP_PERF_ARM_MRVL_PEM_ONLINE,
359 &pem_pmu->node);
360
361 ret = perf_pmu_register(&pem_pmu->pmu, name, -1);
362 if (ret)
363 goto error;
364
365 return 0;
366 error:
367 cpuhp_state_remove_instance_nocalls(CPUHP_AP_PERF_ARM_MRVL_PEM_ONLINE,
368 &pem_pmu->node);
369 return ret;
370 }
371
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-20 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 12:51 [PATCH v7] perf/marvell: Marvell PEM performance monitor support Gowthami Thiagarajan
2024-09-20 3:25 ` kernel test robot
2024-09-20 3:35 ` kernel test robot [this message]
2024-09-20 23:08 ` kernel test robot
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=202409201101.hqshrCE7-lkp@intel.com \
--to=lkp@intel.com \
--cc=gcherian@marvell.com \
--cc=gthiagarajan@marvell.com \
--cc=lcherian@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sgoutham@marvell.com \
--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