From: Marc Zyngier <maz@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Akihiko Odaki <akihiko.odaki@daynix.com>,
Oliver Upton <oliver.upton@linux.dev>,
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>,
Andrew Jones <andrew.jones@linux.dev>,
oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, devel@daynix.com
Subject: Re: [PATCH v5 3/5] KVM: arm64: PMU: Fix SET_ONE_REG for vPMC regs
Date: Mon, 17 Mar 2025 14:49:24 +0000 [thread overview]
Message-ID: <86y0x3n24r.wl-maz@kernel.org> (raw)
In-Reply-To: <202503172023.fzyJ3TMB-lkp@intel.com>
On Mon, 17 Mar 2025 13:02:47 +0000,
kernel test robot <lkp@intel.com> wrote:
>
> Hi Akihiko,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on 80e54e84911a923c40d7bee33a34c1b4be148d7a]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Akihiko-Odaki/KVM-arm64-PMU-Set-raw-values-from-user-to-PM-C-I-NTEN-SET-CLR-PMOVS-SET-CLR/20250315-173731
> base: 80e54e84911a923c40d7bee33a34c1b4be148d7a
> patch link: https://lore.kernel.org/r/20250315-pmc-v5-3-ecee87dab216%40daynix.com
> patch subject: [PATCH v5 3/5] KVM: arm64: PMU: Fix SET_ONE_REG for vPMC regs
> config: arm64-randconfig-r122-20250317 (https://download.01.org/0day-ci/archive/20250317/202503172023.fzyJ3TMB-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 14.2.0
> reproduce: (https://download.01.org/0day-ci/archive/20250317/202503172023.fzyJ3TMB-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/202503172023.fzyJ3TMB-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> arch/arm64/kvm/sys_regs.c: In function 'set_pmu_evcntr':
> >> arch/arm64/kvm/sys_regs.c:975:9: error: implicit declaration of function 'kvm_pmu_set_counter_value_user'; did you mean 'kvm_pmu_set_counter_value'? [-Wimplicit-function-declaration]
> 975 | kvm_pmu_set_counter_value_user(vcpu, idx, val);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | kvm_pmu_set_counter_value
>
>
> vim +975 arch/arm64/kvm/sys_regs.c
>
> 962
> 963 static int set_pmu_evcntr(struct kvm_vcpu *vcpu, const struct sys_reg_desc *r,
> 964 u64 val)
> 965 {
> 966 u64 idx;
> 967
> 968 if (r->CRn == 9 && r->CRm == 13 && r->Op2 == 0)
> 969 /* PMCCNTR_EL0 */
> 970 idx = ARMV8_PMU_CYCLE_IDX;
> 971 else
> 972 /* PMEVCNTRn_EL0 */
> 973 idx = ((r->CRm & 3) << 3) | (r->Op2 & 7);
> 974
> > 975 kvm_pmu_set_counter_value_user(vcpu, idx, val);
> 976 return 0;
> 977 }
> 978
>
Looks like a case of missing stub definitions when
CONFIG_HW_PERF_EVENTS isn't selected.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-03-17 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 9:12 [PATCH v5 0/5] KVM: arm64: PMU: Fix SET_ONE_REG for vPMC regs Akihiko Odaki
2025-03-15 9:12 ` [PATCH v5 1/5] KVM: arm64: PMU: Set raw values from user to PM{C,I}NTEN{SET,CLR}, PMOVS{SET,CLR} Akihiko Odaki
2025-03-15 9:12 ` [PATCH v5 2/5] KVM: arm64: PMU: Assume PMU presence in pmu-emul.c Akihiko Odaki
2025-03-15 9:12 ` [PATCH v5 3/5] KVM: arm64: PMU: Fix SET_ONE_REG for vPMC regs Akihiko Odaki
2025-03-17 13:02 ` kernel test robot
2025-03-17 14:49 ` Marc Zyngier [this message]
2025-03-15 9:12 ` [PATCH v5 4/5] KVM: arm64: PMU: Reload when user modifies registers Akihiko Odaki
2025-03-15 9:12 ` [PATCH v5 5/5] KVM: arm64: PMU: Reload when resetting Akihiko Odaki
2025-03-16 10:33 ` [PATCH v5 0/5] KVM: arm64: PMU: Fix SET_ONE_REG for vPMC regs Marc Zyngier
2025-03-17 20:01 ` Oliver Upton
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=86y0x3n24r.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=akihiko.odaki@daynix.com \
--cc=andrew.jones@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=devel@daynix.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=lkp@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).