linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [arm-platforms:kvm-arm64/pmu-event-filter 4/5] arch/arm64/kvm/sys_regs.c:772:11: error: implicit declaration of function 'kvm_pmu_get_pmceid'
Date: Wed, 2 Sep 2020 00:11:14 +0800	[thread overview]
Message-ID: <202009020010.4luEy0EV%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git kvm-arm64/pmu-event-filter
head:   37f49ef9193707930ce484c9adabe8e586a163a0
commit: f55147a38bcded5c30c5ce6a0bd8b3973bbdb073 [4/5] KVM: arm64: Mask out filtered events in PCMEID{0,1}_EL1
config: arm64-randconfig-r036-20200901 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout f55147a38bcded5c30c5ce6a0bd8b3973bbdb073
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/arm64/kvm/sys_regs.c: In function 'access_pmceid':
>> arch/arm64/kvm/sys_regs.c:772:11: error: implicit declaration of function 'kvm_pmu_get_pmceid' [-Werror=implicit-function-declaration]
     772 |  pmceid = kvm_pmu_get_pmceid(vcpu, (p->Op2 & 1));
         |           ^~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

# https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/commit/?id=f55147a38bcded5c30c5ce6a0bd8b3973bbdb073
git remote add arm-platforms https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
git fetch --no-tags arm-platforms kvm-arm64/pmu-event-filter
git checkout f55147a38bcded5c30c5ce6a0bd8b3973bbdb073
vim +/kvm_pmu_get_pmceid +772 arch/arm64/kvm/sys_regs.c

   758	
   759	static bool access_pmceid(struct kvm_vcpu *vcpu, struct sys_reg_params *p,
   760				  const struct sys_reg_desc *r)
   761	{
   762		u64 pmceid;
   763	
   764		if (!kvm_arm_pmu_v3_ready(vcpu))
   765			return trap_raz_wi(vcpu, p, r);
   766	
   767		BUG_ON(p->is_write);
   768	
   769		if (pmu_access_el0_disabled(vcpu))
   770			return false;
   771	
 > 772		pmceid = kvm_pmu_get_pmceid(vcpu, (p->Op2 & 1));
   773	
   774		p->regval = pmceid;
   775	
   776		return true;
   777	}
   778	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35312 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2020-09-01 16:14 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=202009020010.4luEy0EV%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@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).