From: Paolo Bonzini <pbonzini@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Sean Christopherson <seanjc@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>,
Brijesh Singh <brijesh.singh@amd.com>
Subject: Re: [PATCH] x86/sev: Add AMD_SEV_ES_GUEST Kconfig for including SEV-ES support
Date: Mon, 18 Jan 2021 21:30:35 +0100 [thread overview]
Message-ID: <2262feb0-830e-1e05-d81b-031d54cf6853@redhat.com> (raw)
In-Reply-To: <20210118202611.GH30090@zn.tnic>
On 18/01/21 21:26, Borislav Petkov wrote:
> On Mon, Jan 18, 2021 at 06:59:38PM +0100, Paolo Bonzini wrote:
>> On 16/01/21 01:25, Sean Christopherson wrote:
>>>
>>> @@ -1527,12 +1527,14 @@ config AMD_MEM_ENCRYPT
>>> select DYNAMIC_PHYSICAL_MASK
>>> select ARCH_USE_MEMREMAP_PROT
>>> select ARCH_HAS_FORCE_DMA_UNENCRYPTED
>>> - select INSTRUCTION_DECODER
>>> help
>>> Say yes to enable support for the encryption of system memory.
>>> This requires an AMD processor that supports Secure Memory
>>> Encryption (SME).
>>> + This also enables support for running as a Secure Encrypted
>>> + Virtualization (SEV) guest.
>>> +
>>> config AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT
>>> bool "Activate AMD Secure Memory Encryption (SME) by default"
>>> default y
>>> @@ -1547,6 +1549,15 @@ config AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT
>>> If set to N, then the encryption of system memory can be
>>> activated with the mem_encrypt=on command line option.
>>> +config AMD_SEV_ES_GUEST
>>> + bool "AMD Secure Encrypted Virtualization - Encrypted State (SEV-ES) Guest support"
>>> + depends on AMD_MEM_ENCRYPT
>>> + select INSTRUCTION_DECODER
>>> + help
>>> + Enable support for running as a Secure Encrypted Virtualization -
>>> + Encrypted State (SEV-ES) Guest. This enables SEV-ES boot protocol
>>> + changes, #VC handling, SEV-ES specific hypercalls, etc...
>>> +
>>
>> Queued, thanks.
>
> Say, Paolo, why are you queuing a patch which goes through tip, if at all?
Right you are, unqueued. I would have caught the mistake before
actually crystallizing the hashes, but thanks for noticing!
Sean, please send a v2 that removes the help change for AMD_MEM_ENCRYPT,
too.
Thanks,
Paolo
next prev parent reply other threads:[~2021-01-18 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 0:25 [PATCH] x86/sev: Add AMD_SEV_ES_GUEST Kconfig for including SEV-ES support Sean Christopherson
2021-01-16 5:40 ` Tom Lendacky
2021-01-18 18:03 ` Paolo Bonzini
2021-01-18 18:16 ` Tom Lendacky
2021-01-18 17:59 ` Paolo Bonzini
2021-01-18 20:26 ` Borislav Petkov
2021-01-18 20:30 ` Paolo Bonzini [this message]
2021-01-18 20:29 ` Borislav Petkov
2021-01-18 20:32 ` Paolo Bonzini
2021-01-18 20:47 ` Borislav Petkov
2021-01-19 16:23 ` Sean Christopherson
2021-01-19 17:09 ` Borislav Petkov
2021-01-19 17:12 ` 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=2262feb0-830e-1e05-d81b-031d54cf6853@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--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;
as well as URLs for NNTP newsgroup(s).