Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4211855ybi; Tue, 18 Jun 2019 13:57:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqynGsumYsjNjWQHWjkWAOKi0JMmlE5ad1yfm58BOSAO5O/VKU9WiY/GgKGTlfCelhdZiao/ X-Received: by 2002:a63:ed06:: with SMTP id d6mr4440540pgi.267.1560891478217; Tue, 18 Jun 2019 13:57:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560891478; cv=none; d=google.com; s=arc-20160816; b=ETbiDrj8f/mwqA35AJV0uTt4h93wyKBepJaVjfOTJkv7PKdSUQffdeLhyRZOjbIpDx m9p5Rly8Wro6y/1DpQ/v6/zDWjuyu8858HVEz+R6WBFLZvdBFtDDORH7U8eWfaNBfzFj YtsPF7DlkJsSVcpdzJeIrM/GmI7fvrDHyafdRSAIZmHaeg8ePRz3GzLF//dot/YT4zfU znm+ijJwufaIw4KH/FbG2ZUXKgvCsowMNfAZ1S3knzkiS8+hxvPhU6rOEFEBQyFiaset yLoO69Y5+OICcsz8eyW2v3TuvjbOoBksNt1jShddQGBAOYEg0KNuWTNpOZHn7o1mjqoe n3zw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=LvMZCNqyjGCYorMHMnZsk1Wxffwcw4B9xSPUy6NpG7A=; b=Nv+7g87ILJM1SiXa8hhWDTfV4Pmy71y7VEFm5yYs/sMcxUkdOfqG3X4F+QUPgIeRn2 k8rwKuIU4bAJwiR9kjJCqs2hrjKd9UYtlhJ46xABbpTS1seK7HxVOycwEtNIPt8w9QhC yciwHvsvw+YV2ZI7N76a3re+7lRMk270F16XVauks6WumaylyOMLTWyWZ+EWcZ8JhBFX DagnwOWqh6Otoh/hA689DIOp4pNsMGYV4pFSchoSSjj8gPRHnmW8TLK4F/FrWJBs1Rd2 F3Lf0/8ExP4b4Vb67J06T/FuXXaTNdPGngvNuezY3ZA5cvkgnlYDwfIeEAlkwZHTuhuq wDUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=XVxjWv7H; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i14si1115084pgh.437.2019.06.18.13.57.42; Tue, 18 Jun 2019 13:57:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=XVxjWv7H; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730655AbfFRUxy (ORCPT + 99 others); Tue, 18 Jun 2019 16:53:54 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:50308 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730181AbfFRUxy (ORCPT ); Tue, 18 Jun 2019 16:53:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Message-Id:Date:Subject:Cc: To:From: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=LvMZCNqyjGCYorMHMnZsk1Wxffwcw4B9xSPUy6NpG7A=; b=XVxjWv7HGrfjCzeXzENuLOb9Be g/j6stqYjNL9awd3mSzUb3SVGaavvAwhp6vraHQt0n5pnB3I0iSOoG0wB6kzt7Q2/8ZOHSNE8GMSu dWHdIE4U73bXmCMKEpuhmxu07Q8ou+zWdPmqs3YPVHL5/9tciqLIdJ2Di9FLQg+FGDW2XJVQyv+jW HpI+zI30YxS1o3ABjcd4gs4BXo48//+rOAibs8C91NHoIvurrnc8IMZIez/ET+kftLlNRfS42lALq vZ8nntXoqiKfpap1+Oy8KrRWrXHqXLJo5hdXcCGk4nFGaxaxakkjHrMp4SxdNxqqjHc3mfrL53sVA +51b6aOQ==; Received: from 177.133.86.196.dynamic.adsl.gvt.net.br ([177.133.86.196] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.92 #3 (Red Hat Linux)) id 1hdL73-0008Ml-Eo; Tue, 18 Jun 2019 20:53:53 +0000 Received: from mchehab by bombadil.infradead.org with local (Exim 4.92) (envelope-from ) id 1hdL6z-0001zd-Ux; Tue, 18 Jun 2019 17:53:49 -0300 From: Mauro Carvalho Chehab To: Linux Doc Mailing List Cc: Mauro Carvalho Chehab , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet Subject: [PATCH v2 12/29] docs: xen-tpmfront.txt: convert it to .rst Date: Tue, 18 Jun 2019 17:53:30 -0300 Message-Id: <1c600880caa3344d65ab53b808b7fbb62a8e6fc4.1560890800.git.mchehab+samsung@kernel.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In order to be able to add this file to the security book, we need first to convert it to reST. While this is not part of any book, mark it as :orphan:, in order to avoid build warnings. Signed-off-by: Mauro Carvalho Chehab --- .../{xen-tpmfront.txt => xen-tpmfront.rst} | 103 ++++++++++-------- 1 file changed, 58 insertions(+), 45 deletions(-) rename Documentation/security/tpm/{xen-tpmfront.txt => xen-tpmfront.rst} (66%) diff --git a/Documentation/security/tpm/xen-tpmfront.txt b/Documentation/security/tpm/xen-tpmfront.rst similarity index 66% rename from Documentation/security/tpm/xen-tpmfront.txt rename to Documentation/security/tpm/xen-tpmfront.rst index 69346de87ff3..98a16ab87360 100644 --- a/Documentation/security/tpm/xen-tpmfront.txt +++ b/Documentation/security/tpm/xen-tpmfront.rst @@ -1,4 +1,8 @@ +:orphan: + +============================= Virtual TPM interface for Xen +============================= Authors: Matthew Fioravante (JHUAPL), Daniel De Graaf (NSA) @@ -6,7 +10,8 @@ This document describes the virtual Trusted Platform Module (vTPM) subsystem for Xen. The reader is assumed to have familiarity with building and installing Xen, Linux, and a basic understanding of the TPM and vTPM concepts. -INTRODUCTION +Introduction +------------ The goal of this work is to provide a TPM functionality to a virtual guest operating system (in Xen terms, a DomU). This allows programs to interact with @@ -24,81 +29,89 @@ This mini-os vTPM subsystem was built on top of the previous vTPM work done by IBM and Intel corporation. -DESIGN OVERVIEW +Design Overview --------------- -The architecture of vTPM is described below: +The architecture of vTPM is described below:: -+------------------+ -| Linux DomU | ... -| | ^ | -| v | | -| xen-tpmfront | -+------------------+ - | ^ - v | -+------------------+ -| mini-os/tpmback | -| | ^ | -| v | | -| vtpm-stubdom | ... -| | ^ | -| v | | -| mini-os/tpmfront | -+------------------+ - | ^ - v | -+------------------+ -| mini-os/tpmback | -| | ^ | -| v | | -| vtpmmgr-stubdom | -| | ^ | -| v | | -| mini-os/tpm_tis | -+------------------+ - | ^ - v | -+------------------+ -| Hardware TPM | -+------------------+ + +------------------+ + | Linux DomU | ... + | | ^ | + | v | | + | xen-tpmfront | + +------------------+ + | ^ + v | + +------------------+ + | mini-os/tpmback | + | | ^ | + | v | | + | vtpm-stubdom | ... + | | ^ | + | v | | + | mini-os/tpmfront | + +------------------+ + | ^ + v | + +------------------+ + | mini-os/tpmback | + | | ^ | + | v | | + | vtpmmgr-stubdom | + | | ^ | + | v | | + | mini-os/tpm_tis | + +------------------+ + | ^ + v | + +------------------+ + | Hardware TPM | + +------------------+ - * Linux DomU: The Linux based guest that wants to use a vTPM. There may be +* Linux DomU: + The Linux based guest that wants to use a vTPM. There may be more than one of these. - * xen-tpmfront.ko: Linux kernel virtual TPM frontend driver. This driver +* xen-tpmfront.ko: + Linux kernel virtual TPM frontend driver. This driver provides vTPM access to a Linux-based DomU. - * mini-os/tpmback: Mini-os TPM backend driver. The Linux frontend driver +* mini-os/tpmback: + Mini-os TPM backend driver. The Linux frontend driver connects to this backend driver to facilitate communications between the Linux DomU and its vTPM. This driver is also used by vtpmmgr-stubdom to communicate with vtpm-stubdom. - * vtpm-stubdom: A mini-os stub domain that implements a vTPM. There is a +* vtpm-stubdom: + A mini-os stub domain that implements a vTPM. There is a one to one mapping between running vtpm-stubdom instances and logical vtpms on the system. The vTPM Platform Configuration Registers (PCRs) are normally all initialized to zero. - * mini-os/tpmfront: Mini-os TPM frontend driver. The vTPM mini-os domain +* mini-os/tpmfront: + Mini-os TPM frontend driver. The vTPM mini-os domain vtpm-stubdom uses this driver to communicate with vtpmmgr-stubdom. This driver is also used in mini-os domains such as pv-grub that talk to the vTPM domain. - * vtpmmgr-stubdom: A mini-os domain that implements the vTPM manager. There is +* vtpmmgr-stubdom: + A mini-os domain that implements the vTPM manager. There is only one vTPM manager and it should be running during the entire lifetime of the machine. This domain regulates access to the physical TPM on the system and secures the persistent state of each vTPM. - * mini-os/tpm_tis: Mini-os TPM version 1.2 TPM Interface Specification (TIS) +* mini-os/tpm_tis: + Mini-os TPM version 1.2 TPM Interface Specification (TIS) driver. This driver used by vtpmmgr-stubdom to talk directly to the hardware TPM. Communication is facilitated by mapping hardware memory pages into vtpmmgr-stubdom. - * Hardware TPM: The physical TPM that is soldered onto the motherboard. +* Hardware TPM: + The physical TPM that is soldered onto the motherboard. -INTEGRATION WITH XEN +Integration With Xen -------------------- Support for the vTPM driver was added in Xen using the libxl toolstack in Xen -- 2.21.0