From: Paolo Bonzini <pbonzini@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Brijesh Singh" <brijesh.singh@amd.com>,
"Borislav Petkov" <bp@suse.de>
Subject: Re: [PATCH] KVM: X86: Add missing KVM_AMD dependency
Date: Sat, 6 Oct 2018 00:18:30 +0200 [thread overview]
Message-ID: <713d35b9-5dd5-284f-b514-7d2295a2db34@redhat.com> (raw)
In-Reply-To: <20181005220325.GA24365@roeck-us.net>
On 06/10/2018 00:03, Guenter Roeck wrote:
>> This should be handled by
>>
>> 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.
>>
> Unfortunately it doesn't. It disables KVM_AMD_SEV, but that doesn't prevent
> the calls.
Yes, exactly - that's why I mentioned the sev_guest patch that should
cull all the SEV code from a !KVM_AMD_SEV build.
>> Maybe this works as well? I haven't tested it yet:
>>
> I am sure there are many possible solutions. I would personally prefer one
> that enforces KVM_AMD=m with CRYPTO_DEV_CCP_DD=m, but that is just me.
Well, KVM_AMD=y is a relatively unusual choice to begin with. The
question is whether then you want to disable this choice completely when
CRYPTO_DEV_CCP_DD=m, or just disable SEV.
My patch is a good idea anyway, if I may say so :), because it culls a
lot of code from a !KVM_AMD_SEV build. But if it is not enough, we
certainly have to do something else about the failure you're reporting.
Paolo
next prev parent reply other threads:[~2018-10-05 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 18:46 Guenter Roeck
2018-10-05 20:41 ` Paolo Bonzini
2018-10-05 22:03 ` Guenter Roeck
2018-10-05 22:18 ` Paolo Bonzini [this message]
2018-10-06 20:43 ` Guenter Roeck
2018-10-08 11:27 ` Paolo Bonzini
2018-10-08 14:52 ` Singh, Brijesh
2018-10-08 17:32 ` Borislav Petkov
2018-10-09 16:26 ` 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=713d35b9-5dd5-284f-b514-7d2295a2db34@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®