From: Paolo Bonzini <pbonzini@redhat.com>
To: kbuild test robot <lkp@intel.com>,
Sean Christopherson <sean.j.christopherson@intel.com>
Cc: kbuild-all@01.org, kvm@vger.kernel.org,
Robert Hu <robert.hu@intel.com>,
Farrah Chen <farrah.chen@intel.com>,
Danmei Wei <danmei.wei@intel.com>
Subject: Re: [kvm:queue 104/105] vmx.c:undefined reference to `__udivdi3'
Date: Tue, 18 Jun 2019 12:56:48 +0200 [thread overview]
Message-ID: <467292fe-c1ee-0430-22af-b13cd9cbc559@redhat.com> (raw)
In-Reply-To: <201906180411.jzFP0qva%lkp@intel.com>
On 17/06/19 22:20, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
> head: 5253b5b578e40c3a10922579b38d1a53112324bd
> commit: ce70de9a05de4510435f554da0cb2fb3321ba0fc [104/105] KVM: VMX: Leave preemption timer running when it's disabled
> config: i386-allyesconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> git checkout ce70de9a05de4510435f554da0cb2fb3321ba0fc
> # save the attached .config to linux build tree
> make ARCH=i386
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> ld: arch/x86/kvm/vmx/vmx.o: in function `hardware_setup':
>>> vmx.c:(.init.text+0xe90): undefined reference to `__udivdi3'
Fixed by rewriting
if ((0xffffffffu / use_timer_freq) < 10)
enable_preemption_timer = false;
to
if (use_timer_freq > 0xffffffffu / 10)
enable_preemption_timer = false;
(finally doing inequations in high school paid off).
Paolo
prev parent reply other threads:[~2019-06-18 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 20:20 [kvm:queue 104/105] vmx.c:undefined reference to `__udivdi3' kbuild test robot
2019-06-18 10:56 ` Paolo Bonzini [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=467292fe-c1ee-0430-22af-b13cd9cbc559@redhat.com \
--to=pbonzini@redhat.com \
--cc=danmei.wei@intel.com \
--cc=farrah.chen@intel.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=robert.hu@intel.com \
--cc=sean.j.christopherson@intel.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).