From: Sean Christopherson <sean.j.christopherson@intel.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Ben Gardon <bgardon@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
X86 ML <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
kvm list <kvm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: kvm: x86-32 fails to link with tdp_mmu
Date: Fri, 23 Oct 2020 20:04:09 -0700 [thread overview]
Message-ID: <20201024030409.GD7824@linux.intel.com> (raw)
In-Reply-To: <20201024021754.GC7824@linux.intel.com>
On Fri, Oct 23, 2020 at 07:17:54PM -0700, Sean Christopherson wrote:
> On Fri, Oct 23, 2020 at 09:13:21PM -0500, Daniel Díaz wrote:
> > Hello!
> >
> > We found the following problem building torvalds/master, which
> > recently merged the for-linus tag from the KVM tree, when building
> > with gcc 7.3.0 and glibc 2.27 for x86 32-bits under OpenEmbedded:
> >
> > | LD vmlinux.o
> > | MODPOST vmlinux.symvers
> > | MODINFO modules.builtin.modinfo
> > | GEN modules.builtin
> > | LD .tmp_vmlinux.kallsyms1
> > | arch/x86/kvm/mmu/tdp_mmu.o: In function `__handle_changed_spte':
> > | tdp_mmu.c:(.text+0x78a): undefined reference to `__umoddi3'
>
> The problem is a % on a 64-bit value. Patches incoming, there's also a goof
> in similar code that was tweaked last minute to avoid the %.
Just the one patch actually, I misread some cleverness. Patch still inbound...
prev parent reply other threads:[~2020-10-24 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 2:13 kvm: x86-32 fails to link with tdp_mmu Daniel Díaz
2020-10-24 2:17 ` Sean Christopherson
2020-10-24 3:04 ` Sean Christopherson [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=20201024030409.GD7824@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bgardon@google.com \
--cc=bp@alien8.de \
--cc=daniel.diaz@linaro.org \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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.