Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [rppt:gfp-to-kmalloc/v0.1 234/238] arch/x86/xen/pmu.c:551:52: error: too few arguments provided to function-like macro invocation
Date: Wed, 20 May 2026 05:32:40 +0800	[thread overview]
Message-ID: <202605200546.bZPeSOBS-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git gfp-to-kmalloc/v0.1
head:   cf8f69ff9142effba4d8d9a70a1a4f275044376c
commit: 04507bba0f5ca2d399ac98b495682a381b669c27 [234/238] x86/xen/msr: replace get_zeroed_page() with kzalloc()
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20260520/202605200546.bZPeSOBS-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260520/202605200546.bZPeSOBS-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/202605200546.bZPeSOBS-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/x86/xen/pmu.c:551:52: error: too few arguments provided to function-like macro invocation
     551 |         kfree((void *)(unsigned long)per_cpu(xenpmu_shared).xenpmu_data, 0);
         |                                                           ^
   include/linux/percpu-defs.h:273:9: note: macro 'per_cpu' defined here
     273 | #define per_cpu(var, cpu)       (*per_cpu_ptr(&(var), cpu))
         |         ^
>> arch/x86/xen/pmu.c:551:31: error: use of undeclared identifier 'per_cpu'
     551 |         kfree((void *)(unsigned long)per_cpu(xenpmu_shared).xenpmu_data, 0);
         |                                      ^
   2 errors generated.


vim +551 arch/x86/xen/pmu.c

   537	
   538	void xen_pmu_finish(int cpu)
   539	{
   540		struct xen_pmu_params xp;
   541	
   542		if (xen_hvm_domain())
   543			return;
   544	
   545		xp.vcpu = cpu;
   546		xp.version.maj = XENPMU_VER_MAJ;
   547		xp.version.min = XENPMU_VER_MIN;
   548	
   549		(void)HYPERVISOR_xenpmu_op(XENPMU_finish, &xp);
   550	
 > 551		kfree((void *)(unsigned long)per_cpu(xenpmu_shared).xenpmu_data, 0);

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

                 reply	other threads:[~2026-05-19 21:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202605200546.bZPeSOBS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rppt@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