[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210118204701.GJ30090@zn.tnic>
Date: Mon, 18 Jan 2021 21:47:01 +0100
From: Borislav Petkov <bp@...en8.de>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Sean Christopherson <seanjc@...gle.com>,
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 Mon, Jan 18, 2021 at 09:32:07PM +0100, Paolo Bonzini wrote:
> I think it makes sense because AMD_SEV_ES_GUEST's #VC handling is quite a
> bit of code that you may not want or need.
Quite a bit of code which ends up practically enabled on the majority of
distros.
And it ain't about savings of whopping KiBs. And yet another Kconfig symbol
in our gazillion Kconfig symbols space means ugly ifdeffery and paying
attention to randconfig builds.
For tailored configs you simply disable AMD_MEM_ENCRYPT on !AMD hw and
all done.
So I don't see the point for this.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists