Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2766807yba; Mon, 15 Apr 2019 20:00:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqyqR0AoTW99C8HbXmuyThwTCx9a5x21b1g2oj8Nrlvop8Zyc/iBndFe96K35h4Mwr73i/1c X-Received: by 2002:a62:62c3:: with SMTP id w186mr47538016pfb.73.1555383630041; Mon, 15 Apr 2019 20:00:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555383630; cv=none; d=google.com; s=arc-20160816; b=aibErRmp5J2dWUVq6qXoWE5NE0mDmh0sI83m7cwHy6uieJMsDle6mYM3lun/KYVo1N jyUAalaS8oEx8Xyw7C7JctFOMjBml6F5KTr0Ih4YzpS6KyB14453HzNLdanibeumjRsC JedE/58QyMlbutcJ7RRcLASRLoP/04jHQg/cs+NKqJ12xwa0zk7FrMrh+9aGFYeMwQDi 84szTwgjZ2CmIEup6FVQ9sBtHgZ6Px+s072VR3xJ+zctx3MygZiRP+LJm72vugaghEKl FwMqzQ1yu7hrMCks5iORJpEzvK0JaDS0q3bmHRuQod9pvoweg6l9Orelbdd4osufbl9r jSRQ== 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=q5BvRKNC5E2Z4qAZ/NkoF5aANDSgRkCrhT52rDcWEzI=; b=kx5Wlk5tm9mo2uZNgkJ9iyTQqTHK3a92P8dmQFX/tDoJYy25UgVKuEy4+ESOuNWRWC 9swzgmRkMNgYaGdot2k6usXDpZqfS5VXiOcmysTpZHTXonlo+54TQJEnZkgRUTOTtls4 1XENxCgy2NK8Fz+XJPyM2NbJaiySWFmmOj4cccMFqi4fJl1kUtMDHEi5blNjZvQuG5av pwmIpOlDUJWm9iudKEOPU9UU0Cj54nhj5y18jGTtXKMzwuxJlcYAanGI3uWnI5juVYDR JqwcPRMDW7mA9Uz13F10Q9PVX583zgCe391EPRgkCni5q6Idom4+luVwVzBspgifeoKK 7qdw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=hTQNqW1F; 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 a3si49266109pln.353.2019.04.15.20.00.13; Mon, 15 Apr 2019 20:00:30 -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=hTQNqW1F; 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 S1728400AbfDPC4q (ORCPT + 99 others); Mon, 15 Apr 2019 22:56:46 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:44534 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726924AbfDPC4g (ORCPT ); Mon, 15 Apr 2019 22:56:36 -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=q5BvRKNC5E2Z4qAZ/NkoF5aANDSgRkCrhT52rDcWEzI=; b=hTQNqW1F1B8i/59leVyUh42/DH ZKlJDd+g6JNAVZxsbpis2Yx86VtUkMX+G1H3GXqYmaHDma/7nWQYsnkGpF190EvE9EW87Y3/BSgg+ XcOOtIWL8JLCKjUIeV5PQ81opp9qxvjcQFb1SVQl0jZZAflk+6AIAS3eq7+JpqZ+JolBtYgJvDDEm qhY8K51GSz0kOjKmTsKDUMlJ6lhBYBDj+RLmaKICX6ye5Fxux1hKF6mQwbOMwxnBRsrQnn4wA8EJT f1JBnGa7tpKkq9CNYs8utvolYcHeCuI9OnQZDZaQ0bWhG0a2gR2d+SUNxq++dEfU+oDnMhkWuijVa DRmLwncA==; Received: from 177.205.118.176.dynamic.adsl.gvt.net.br ([177.205.118.176] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hGEGw-0007aV-JP; Tue, 16 Apr 2019 02:56:34 +0000 Received: from mchehab by bombadil.infradead.org with local (Exim 4.92) (envelope-from ) id 1hGEGo-0001q6-CY; Mon, 15 Apr 2019 23:56:26 -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 53/57] docs: xen-tpmfront.txt: convert the file to ReST format Date: Mon, 15 Apr 2019 23:56:18 -0300 Message-Id: <89981957b7ab12fa6e6c392b4b39fbc5ea08f139.1555382110.git.mchehab+samsung@kernel.org> X-Mailer: git-send-email 2.20.1 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. Signed-off-by: Mauro Carvalho Chehab --- Documentation/security/tpm/xen-tpmfront.txt | 101 +++++++++++--------- 1 file changed, 56 insertions(+), 45 deletions(-) diff --git a/Documentation/security/tpm/xen-tpmfront.txt b/Documentation/security/tpm/xen-tpmfront.txt index 69346de87ff3..00d5b1db227d 100644 --- a/Documentation/security/tpm/xen-tpmfront.txt +++ b/Documentation/security/tpm/xen-tpmfront.txt @@ -1,4 +1,6 @@ +============================= Virtual TPM interface for Xen +============================= Authors: Matthew Fioravante (JHUAPL), Daniel De Graaf (NSA) @@ -6,7 +8,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 +27,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.20.1