[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fcb7a13b-bbac-be8c-730c-889b18f98598@redhat.com>
Date: Tue, 19 Jan 2021 18:12:28 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Borislav Petkov <bp@...en8.de>,
Sean Christopherson <seanjc@...gle.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
"H. Peter Anvin" <hpa@...or.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Tom Lendacky <thomas.lendacky@....com>,
Brijesh Singh <brijesh.singh@....com>
Subject: Re: [PATCH] x86/sev: Add AMD_SEV_ES_GUEST Kconfig for including
SEV-ES support
On 19/01/21 18:09, Borislav Petkov wrote:
>> It was the AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT dependency that tripped me up. To
>> get KVM to enable SEV/SEV-ES by default,
> By default? What would be the use case for that?
It doesn't enable by default SEV/SEV-ES for all the guests, it only
enables the functionality.
But tying that to a Kconfig value is useless, it should just default to
1 (allow creating encrypted guests) if the hardware is available.
Paolo
Powered by blists - more mailing lists