From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brijesh Singh Subject: Re: [Part2 PATCH v6 01/38] Documentation/virtual/kvm: Add AMD Secure Encrypted Virtualization (SEV) Date: Mon, 23 Oct 2017 17:40:47 -0500 Message-ID: References: <20171020023413.122280-1-brijesh.singh@amd.com> <20171020023413.122280-2-brijesh.singh@amd.com> <20171020071807.3e771d3c@lwn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: brijesh.singh@amd.com, kvm@vger.kernel.org, bp@alien8.de, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Borislav Petkov , Tom Lendacky , x86@kernel.org, linux-kernel@vger.kernel.org To: Jonathan Corbet Return-path: Received: from mail-by2nam01on0085.outbound.protection.outlook.com ([104.47.34.85]:18080 "EHLO NAM01-BY2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751200AbdJWWky (ORCPT ); Mon, 23 Oct 2017 18:40:54 -0400 In-Reply-To: <20171020071807.3e771d3c@lwn.net> Content-Language: en-US Sender: kvm-owner@vger.kernel.org List-ID: On 10/20/2017 08:18 AM, Jonathan Corbet wrote: > On Thu, 19 Oct 2017 21:33:36 -0500 > Brijesh Singh wrote: > >> Create a Documentation entry to describe the AMD Secure Encrypted >> Virtualization (SEV) feature. > > A couple of quick notes... > > - This is describing an x86 subarchitecture feature, so it seems to me > that Documentation/x86 would be a more logical place for it. Yes, KVM > can use this feature, but it's not a KVM feature and there might be > something else that takes advantage of it too. > In part1 of SEV patches, we do expand the Documentation/x86/amd-memory-eencryption.txt to explain the SEV architecture feature. In this patch, we focus on documenting the SEV specific changes from the KVM point of view and how it integrate with KVM. > - Any chance of getting it formatted as RST? It's almost there already. > Sure, next rev I will convert it to RST format. > Beyond that, the document obviously falls far short of what one would > have to know to use SEV; probably filling all that in would make it long > indeed. > In later part of patches (Patch 24/38 [1]), I expand this doc to provide high level overview of various SEV commands to support common lifecycle events of SEV guests, such as launching, running, snapshotting, migrating etc. [1] https://patchwork.kernel.org/patch/10018671/