From: "Xu, Like" <like.xu@intel.com>
To: Uros Bizjak <ubizjak@gmail.com>, kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Current mainline kernel FTBFS in KVM SEV
Date: Thu, 9 Apr 2020 16:31:11 +0800 [thread overview]
Message-ID: <8079b118-1ff4-74a8-7010-0601d211a221@intel.com> (raw)
In-Reply-To: <CAFULd4adXFX+y6eCV0tVhg-iHZe+tAchJkuHMXe3ZWktzGk7Sw@mail.gmail.com>
Hi Bizjak,
would you mind telling us the top commit ID in your kernel tree ?
Or you may try the queue branch of
https://git.kernel.org/pub/scm/virt/kvm/kvm.git
and check if this "undefined reference" issue gets fixed.
Thanks,
Like Xu
On 2020/4/9 16:20, Uros Bizjak wrote:
> Current mainline kernel fails to build (on Fedora 31) with:
>
> GEN .version
> CHK include/generated/compile.h
> LD vmlinux.o
> MODPOST vmlinux.o
> MODINFO modules.builtin.modinfo
> GEN modules.builtin
> LD .tmp_vmlinux.btf
> ld: arch/x86/kvm/svm/sev.o: in function `sev_flush_asids':
> /hdd/uros/git/linux/arch/x86/kvm/svm/sev.c:48: undefined reference to
> `sev_guest_df_flush'
> ld: arch/x86/kvm/svm/sev.o: in function `sev_hardware_setup':
> /hdd/uros/git/linux/arch/x86/kvm/svm/sev.c:1146: undefined reference
> to `sev_platform_status'
> BTF .btf.vmlinux.bin.o
>
> .config is attached.
>
> Uros.
next prev parent reply other threads:[~2020-04-09 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 8:20 Current mainline kernel FTBFS in KVM SEV Uros Bizjak
2020-04-09 8:31 ` Xu, Like [this message]
2020-04-09 8:34 ` Uros Bizjak
2020-04-09 11:24 ` Uros Bizjak
2020-04-09 8:33 ` Paolo Bonzini
2020-04-09 8:46 ` Uros Bizjak
2020-04-09 12:51 ` Uros Bizjak
2020-04-09 13:36 ` Paolo Bonzini
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=8079b118-1ff4-74a8-7010-0601d211a221@intel.com \
--to=like.xu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=ubizjak@gmail.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 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.