All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-6.1 6541/11251] arch/arm64/kvm/hyp/nvhe/clock.c:39:undefined reference to `__kvm_nvhe___lshrti3'
Date: Wed, 30 Aug 2023 06:31:38 +0800	[thread overview]
Message-ID: <202308300622.vFMKCQLx-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android14-6.1
head:   e44e3955f7e78d5609a5c472bb261adbef142d63
commit: 022b2198fc73b7b95231730eb944d74c7f1b253c [6541/11251] ANDROID: KVM: arm64: Add clock support in the nVHE hyp
config: arm64-randconfig-r023-20230830 (https://download.01.org/0day-ci/archive/20230830/202308300622.vFMKCQLx-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230830/202308300622.vFMKCQLx-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/202308300622.vFMKCQLx-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: ID map text too big or misaligned
   aarch64-linux-ld: arch/arm64/kvm/hyp/nvhe/kvm_nvhe.o: in function `__kvm_nvhe_trace_clock':
>> arch/arm64/kvm/hyp/nvhe/clock.c:39:(.hyp.text+0x14648): undefined reference to `__kvm_nvhe___lshrti3'


vim +39 arch/arm64/kvm/hyp/nvhe/clock.c

    21	
    22	/*
    23	 * This clock is relying on host provided slope and epoch values to return
    24	 * something synchronized with the host. The downside is we can't trust the
    25	 * output which must not be used for anything else than debugging.
    26	 */
    27	u64 trace_clock(void)
    28	{
    29		u64 cyc = __arch_counter_get_cntpct() - trace_clock_data.epoch_cyc;
    30		__uint128_t ns;
    31	
    32		/*
    33		 * The host kernel can avoid the 64-bits overflow of the multiplication
    34		 * by updating the epoch value with a timer (see
    35		 * kernel/time/clocksource.c). The hypervisor doesn't have that option,
    36		 * so let's do a more costly 128-bits mult here.
    37		 */
    38		ns = (__uint128_t)cyc * trace_clock_data.mult;
  > 39		ns >>= trace_clock_data.shift;

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

                 reply	other threads:[~2023-08-29 22:32 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=202308300622.vFMKCQLx-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.