From: Marc Zyngier <maz@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 11762/12208] drivers/perf/arm_pmuv3.c:776: undefined reference to `kvm_vcpu_pmu_resync_el0'
Date: Thu, 24 Aug 2023 09:14:24 +0100 [thread overview]
Message-ID: <3e5319a59f74856b2ad5db9c22e033ec@kernel.org> (raw)
In-Reply-To: <202308240834.9JkuU1vW-lkp@intel.com>
On 2023-08-24 01:11, kernel test robot wrote:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> head: e3f80d3eae76c3557b3c9b5938ad01c0e6cf25ec
> commit: b1f778a223a2a8ad6262e5233cfc3483bcf6e213 [11762/12208] KVM:
> arm64: pmu: Resync EL0 state on counter rotation
> config: arm64-randconfig-r011-20230823
> (https://download.01.org/0day-ci/archive/20230824/202308240834.9JkuU1vW-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 12.3.0
> reproduce:
> (https://download.01.org/0day-ci/archive/20230824/202308240834.9JkuU1vW-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/202308240834.9JkuU1vW-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> aarch64-linux-ld: Unexpected GOT/PLT entries detected!
> aarch64-linux-ld: Unexpected run-time procedure linkages detected!
> aarch64-linux-ld: drivers/perf/arm_pmuv3.o: in function
> `armv8pmu_start':
>>> drivers/perf/arm_pmuv3.c:776: undefined reference to
>>> `kvm_vcpu_pmu_resync_el0'
This should be fixed in today's -next, which contains 9b80b9676be9
("KVM: arm64: pmu: Guard PMU emulation definitions with CONFIG_KVM").
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2023-08-24 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 0:11 kernel test robot
2023-08-24 8:14 ` Marc Zyngier [this message]
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=3e5319a59f74856b2ad5db9c22e033ec@kernel.org \
--to=maz@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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