From: Uros Bizjak <ubizjak@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>, like.xu@intel.com
Cc: kvm@vger.kernel.org
Subject: Re: Current mainline kernel FTBFS in KVM SEV
Date: Thu, 9 Apr 2020 14:51:30 +0200 [thread overview]
Message-ID: <CAFULd4YG1Df_1HvjDUYCyW+VTLO3-xk8CU4Lwsv2Lq=G-wP+cQ@mail.gmail.com> (raw)
In-Reply-To: <a2187cc0-cab6-78db-3e2d-6edaf647c882@redhat.com>
On Thu, Apr 9, 2020 at 10:33 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 09/04/20 10: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
>
> Strange, the functions are defined and exported with
> CONFIG_CRYPTO_DEV_SP_PSP, which is "y" in your config.
The problem is with
CONFIG_CRYPTO_DEV_CCP_DD=m
in combination with
CONFIG_KVM_AMD=y
in arch/x86/kvmKconfig, there is:
--cut here--
config KVM_AMD_SEV
def_bool y
bool "AMD Secure Encrypted Virtualization (SEV) support"
depends on KVM_AMD && X86_64
depends on CRYPTO_DEV_SP_PSP && !(KVM_AMD=y && CRYPTO_DEV_CCP_DD=m)
---help---
Provides support for launching Encrypted VMs on AMD processors.
--cut here--
which doesn't disable the compilation of sev.o. The missing functions
are actually in ccp.o *module*, called from built-in functions of
sev.o
Enabling CRYPTO_DEV_CCP_DD=y as a built-in instead of a module fixes the build.
Uros.
next prev parent reply other threads:[~2020-04-09 12:51 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
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 [this message]
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='CAFULd4YG1Df_1HvjDUYCyW+VTLO3-xk8CU4Lwsv2Lq=G-wP+cQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu@intel.com \
--cc=pbonzini@redhat.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.