From: kernel test robot <lkp@intel.com>
To: Oliver Upton <oliver.upton@linux.dev>, kvmarm@lists.linux.dev
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Oliver Upton <oliver.upton@linux.dev>
Subject: Re: [PATCH v4 10/18] KVM: arm64: nv: Describe trap behaviour of MDCR_EL2.HPMN
Date: Sat, 26 Oct 2024 18:21:14 +0800 [thread overview]
Message-ID: <202410261855.fvLOtls9-lkp@intel.com> (raw)
In-Reply-To: <20241025182354.3364124-11-oliver.upton@linux.dev>
Hi Oliver,
kernel test robot noticed the following build errors:
[auto build test ERROR on 8e929cb546ee42c9a61d24fae60605e9e3192354]
url: https://github.com/intel-lab-lkp/linux/commits/Oliver-Upton/KVM-arm64-Extend-masking-facility-to-arbitrary-registers/20241026-023055
base: 8e929cb546ee42c9a61d24fae60605e9e3192354
patch link: https://lore.kernel.org/r/20241025182354.3364124-11-oliver.upton%40linux.dev
patch subject: [PATCH v4 10/18] KVM: arm64: nv: Describe trap behaviour of MDCR_EL2.HPMN
config: arm64-randconfig-003-20241026 (https://download.01.org/0day-ci/archive/20241026/202410261855.fvLOtls9-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 5886454669c3c9026f7f27eab13509dd0241f2d6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241026/202410261855.fvLOtls9-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/202410261855.fvLOtls9-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/arm64/kvm/emulate-nested.c:8:
In file included from include/linux/kvm_host.h:16:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
>> arch/arm64/kvm/emulate-nested.c:532:35: error: too many arguments to function call, expected single argument 'vcpu', have 2 arguments
532 | if (kvm_pmu_counter_is_hyp(vcpu, idx))
| ~~~~~~~~~~~~~~~~~~~~~~ ^~~
include/kvm/arm_pmu.h:191:20: note: 'kvm_pmu_counter_is_hyp' declared here
191 | static inline bool kvm_pmu_counter_is_hyp(struct kvm_vcpu *vcpu)
| ^ ~~~~~~~~~~~~~~~~~~~~~
1 warning and 1 error generated.
vim +/vcpu +532 arch/arm64/kvm/emulate-nested.c
509
510 static enum trap_behaviour check_mdcr_hpmn(struct kvm_vcpu *vcpu)
511 {
512 u32 sysreg = esr_sys64_to_sysreg(kvm_vcpu_get_esr(vcpu));
513 unsigned int idx;
514
515
516 switch (sysreg) {
517 case SYS_PMEVTYPERn_EL0(0) ... SYS_PMEVTYPERn_EL0(30):
518 case SYS_PMEVCNTRn_EL0(0) ... SYS_PMEVCNTRn_EL0(30):
519 idx = (sys_reg_CRm(sysreg) & 0x3) << 3 | sys_reg_Op2(sysreg);
520 break;
521 case SYS_PMXEVTYPER_EL0:
522 case SYS_PMXEVCNTR_EL0:
523 idx = SYS_FIELD_GET(PMSELR_EL0, SEL,
524 __vcpu_sys_reg(vcpu, PMSELR_EL0));
525 break;
526 default:
527 /* Someone used this trap helper for something else... */
528 KVM_BUG_ON(1, vcpu->kvm);
529 return BEHAVE_HANDLE_LOCALLY;
530 }
531
> 532 if (kvm_pmu_counter_is_hyp(vcpu, idx))
533 return BEHAVE_FORWARD_RW | BEHAVE_IN_HOST_EL0;
534
535 return BEHAVE_HANDLE_LOCALLY;
536 }
537
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-10-26 10:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20241025182354.3364124-11-oliver.upton@linux.dev>]
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=202410261855.fvLOtls9-lkp@intel.com \
--to=lkp@intel.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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