From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2A616C74A44 for ; Sun, 14 Jul 2019 18:16:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 056F420644 for ; Sun, 14 Jul 2019 18:16:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="EzYn0T6m" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728473AbfGNSQw (ORCPT ); Sun, 14 Jul 2019 14:16:52 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:48096 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726813AbfGNSQw (ORCPT ); Sun, 14 Jul 2019 14:16:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Content-Transfer-Encoding: Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To: Subject:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=zu9VDO3r7C4z6bPiJPIw5Tkj2wZpny80iXDdtymKYFo=; b=EzYn0T6mC7FKpTJ8RU1irxwHC abpmpCrn+ITOcYgj8BJxZSu6aQ8Ii0YPXkA/exU0YQAy7O0m7+zOGJ3xNtG1HVipow4mEY+2R1QFW yUWv1Dom4OKQzrTOt/MbgsA7dNej/caTkqZhPY4jTEfuejInIA0Otu3kOtE0Y3OFmGhYzyRNA53ot 8i1Xw/ye+rilRjaF2MiA8RFIjxQIlV1yRtosHFLPp461r/jWR4weAEdfgWYgXPKwsg7h9oaNby5Uw Fhn/WXJUh22ci0+2oOYbAzeIHC8bxLEX5nMuy4O4wttLhW0+1HBbETWT8w+KVWUyajs2GLcky3C/l obC02yThg==; Received: from static-50-53-52-16.bvtn.or.frontiernet.net ([50.53.52.16] helo=[192.168.1.17]) by bombadil.infradead.org with esmtpsa (Exim 4.92 #3 (Red Hat Linux)) id 1hmj3K-000704-J9; Sun, 14 Jul 2019 18:16:50 +0000 Subject: Re: [PATCH, RFC 57/62] x86/mktme: Overview of Multi-Key Total Memory Encryption To: "Kirill A. Shutemov" , Andrew Morton , x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Borislav Petkov , Peter Zijlstra , Andy Lutomirski , David Howells Cc: Kees Cook , Dave Hansen , Kai Huang , Jacob Pan , Alison Schofield , linux-mm@kvack.org, kvm@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org References: <20190508144422.13171-1-kirill.shutemov@linux.intel.com> <20190508144422.13171-58-kirill.shutemov@linux.intel.com> From: Randy Dunlap Message-ID: Date: Sun, 14 Jul 2019 11:16:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <20190508144422.13171-58-kirill.shutemov@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 5/8/19 7:44 AM, Kirill A. Shutemov wrote: > From: Alison Schofield > > Provide an overview of MKTME on Intel Platforms. > > Signed-off-by: Alison Schofield > Signed-off-by: Kirill A. Shutemov > --- > Documentation/x86/mktme/index.rst | 8 +++ > Documentation/x86/mktme/mktme_overview.rst | 57 ++++++++++++++++++++++ > 2 files changed, 65 insertions(+) > create mode 100644 Documentation/x86/mktme/index.rst > create mode 100644 Documentation/x86/mktme/mktme_overview.rst > diff --git a/Documentation/x86/mktme/mktme_overview.rst b/Documentation/x86/mktme/mktme_overview.rst > new file mode 100644 > index 000000000000..59c023965554 > --- /dev/null > +++ b/Documentation/x86/mktme/mktme_overview.rst > @@ -0,0 +1,57 @@ > +Overview > +========= ... > +-- > +1. https://software.intel.com/sites/default/files/managed/a5/16/Multi-Key-Total-Memory-Encryption-Spec.pdf > +2. The MKTME architecture supports up to 16 bits of KeyIDs, so a > + maximum of 65535 keys on top of the “TME key” at KeyID-0. The > + first implementation is expected to support 5 bits, making 63 Hi, How do 5 bits make 63 keys available? > + keys available to applications. However, this is not guaranteed. > + The number of available keys could be reduced if, for instance, > + additional physical address space is desired over additional > + KeyIDs. thanks. -- ~Randy