From patchwork Mon Feb 26 19:03:34 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Paolo Bonzini X-Patchwork-Id: 206860 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:a81b:b0:108:e6aa:91d0 with SMTP id bq27csp2277338dyb; Mon, 26 Feb 2024 11:06:27 -0800 (PST) X-Forwarded-Encrypted: i=3; AJvYcCV12IaPnR4ZefzKqAsqj1a5yl0SjnUVnLW9Gx+WhDcD4rivo4TWArs8VMyJg8YShul384aZndUL9Vmk3OIL0ZgrMI/b/w== X-Google-Smtp-Source: AGHT+IHzatlAVIxwjsh9uTE3pdyA+5kT0FqEfJQXAlDyaixfZaAW3ZRGIOLsQZQZ5n3KatqtOagf X-Received: by 2002:a05:6358:2613:b0:17b:5c7a:f850 with SMTP id l19-20020a056358261300b0017b5c7af850mr8764479rwc.9.1708974387693; Mon, 26 Feb 2024 11:06:27 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1708974387; cv=pass; d=google.com; s=arc-20160816; b=S/xFYuMmYzEqGzCR9esr5xmJnryX+7XLcCCnQ4fzD1fF825S0rerGo1P4J+ZW/3kES SvwahdDeb/nGxNuIHRl9eXVSyR9rXvfVJQTXbZWgLwrViBilJrptGni9deIlglw5hy5/ C+c2GVM/vHhdViY3i0UwbtF7PM89+tQjCTRtdRtRO3AgfwZBeaP8Dw5xRFzZ7lhcmc/L HrwSKlI4qsG6A4WahIKc97a/xEIxr6SvAtI5S9mjST702vcRy9bsuwQM3nzd5hHSNRgX q7AGxxmDbimeCxrJtbj+DJ6P2a3pWCWxUosCaUESUHgh/RDqExP2+v+7UHDgT1uhRJV8 d87Q== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=CWYUyy6QSMyEARa+J67wigDGH6VAlgHZBuIPAO+RHiQ=; fh=TLdZJsFzSA0fpm6Q4iUv+uB0sG0oU+h3Bp6HiSGyZm8=; b=eKwdMOChueHbxv4crGB4i1rcuoYVXjcWgdVFEQIlO5yb8p4I07SzvHAGJkWUQYM00z ykvAAwJSWgV19O5NABpRRv9kCkmxEClWedEohV7d3YBbEBCpDIsRL6xjU/8c66JwItqj pRrdyk69smSm8Iurzpk1feBhNU5927BueJ/0a7Pr0peOpkBJy6ci+s5edZThPLlMoc3v o8sli+hagklUywZNd2JlhDLPiCo4+H/PXevySMVgc9mN/sZxav2/NUK5ivqrT7Y8fFaL 1mIVAjo0VXCrvRy8QWSqLSKxt9G4Y6FNW9iBykqya0B+Lq7Q3QOG+odfiKXaiVFQdkS6 sClQ==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PjPzMTm7; arc=pass (i=1 spf=pass spfdomain=redhat.com dkim=pass dkdomain=redhat.com dmarc=pass fromdomain=redhat.com); spf=pass (google.com: domain of linux-kernel+bounces-82185-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-82185-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id m3-20020a05620a24c300b007873af4a4e7si6389498qkn.764.2024.02.26.11.06.27 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Feb 2024 11:06:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-82185-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PjPzMTm7; arc=pass (i=1 spf=pass spfdomain=redhat.com dkim=pass dkdomain=redhat.com dmarc=pass fromdomain=redhat.com); spf=pass (google.com: domain of linux-kernel+bounces-82185-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-82185-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 79AB51C22F49 for ; Mon, 26 Feb 2024 19:06:27 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 5A43D132488; Mon, 26 Feb 2024 19:03:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="PjPzMTm7" Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8D62C12FB25 for ; Mon, 26 Feb 2024 19:03:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708974234; cv=none; b=HeoA+CS9VLXoWq8V8BEX6Dp9SOmPfy2S5c4rmHRy0YjnQDs6Wd2WYRRM9uHgy+0Q/P58mQ6cY/E8COi5oGdqx5e97ubatp3BgfqzO5SvTvP3J2b0eTG29RbLmoJSHlCV4XDaLShsMXISVPM49JBOygUi+7VyPZQX2kyiD2sEmzw= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708974234; c=relaxed/simple; bh=BcyNPcEjNpDKmi3eYP5q+XdH/eR7f5WZMjnLtuWyvjc=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=iHBnwQJBcMWfUpE+BDhZrfWYLMO/odq6jVCFgoT3+TvimeWh1PPDr8H7ZSZNAhnJkMQ60mKIJefrXNLuWgth+pLChmy5NPOWTGaV9gpAWfX6ZOKf8peF8kIPNJzwe0bc7KqeIpOOoeKPPLOQ3EL/gmRhIpevmEkxRDSd5gvD69k= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=PjPzMTm7; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1708974231; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CWYUyy6QSMyEARa+J67wigDGH6VAlgHZBuIPAO+RHiQ=; b=PjPzMTm7X0OjcNlddgIFc27fg3Pn3Z0I8ObMCVM4AfOKtdS2inggKzVEvG3OvnAORuCLF/ wFLYVFsiFuNZc6JGQbHi44F42gAt73NR0Z6k9c31QN0jRhQ6O0Uy6dWVmzNIiFhomrHb5A ajIwsekOmetwfTzgE6dgI+Xayusm6pM= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-191-DqbIcuQjPouthjs0p7X-1w-1; Mon, 26 Feb 2024 14:03:47 -0500 X-MC-Unique: DqbIcuQjPouthjs0p7X-1w-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A80D938212D4; Mon, 26 Feb 2024 19:03:46 +0000 (UTC) Received: from virtlab701.virt.lab.eng.bos.redhat.com (virtlab701.virt.lab.eng.bos.redhat.com [10.19.152.228]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7F719492BC6; Mon, 26 Feb 2024 19:03:46 +0000 (UTC) From: Paolo Bonzini To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: seanjc@google.com, michael.roth@amd.com, aik@amd.com Subject: [PATCH v3 05/15] Documentation: kvm/sev: separate description of firmware Date: Mon, 26 Feb 2024 14:03:34 -0500 Message-Id: <20240226190344.787149-6-pbonzini@redhat.com> In-Reply-To: <20240226190344.787149-1-pbonzini@redhat.com> References: <20240226190344.787149-1-pbonzini@redhat.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1791989527263602281 X-GMAIL-MSGID: 1791989527263602281 The description of firmware is included part under the "SEV Key Management" header, part under the KVM_SEV_INIT ioctl. Put these two bits together and and rename "SEV Key Management" to what it actually is, namely a description of the KVM_MEMORY_ENCRYPT_OP API. Reviewed-by: Michael Roth Signed-off-by: Paolo Bonzini Reviewed-by: Bagas Sanjaya --- .../virt/kvm/x86/amd-memory-encryption.rst | 29 +++++++++++-------- 1 file changed, 17 insertions(+), 12 deletions(-) diff --git a/Documentation/virt/kvm/x86/amd-memory-encryption.rst b/Documentation/virt/kvm/x86/amd-memory-encryption.rst index 995780088eb2..37c5c37f4f6e 100644 --- a/Documentation/virt/kvm/x86/amd-memory-encryption.rst +++ b/Documentation/virt/kvm/x86/amd-memory-encryption.rst @@ -46,14 +46,8 @@ SEV hardware uses ASIDs to associate a memory encryption key with a VM. Hence, the ASID for the SEV-enabled guests must be from 1 to a maximum value defined in the CPUID 0x8000001f[ecx] field. -SEV Key Management -================== - -The SEV guest key management is handled by a separate processor called the AMD -Secure Processor (AMD-SP). Firmware running inside the AMD-SP provides a secure -key management interface to perform common hypervisor activities such as -encrypting bootstrap code, snapshot, migrating and debugging the guest. For more -information, see the SEV Key Management spec [api-spec]_ +``KVM_MEMORY_ENCRYPT_OP`` API +============================= The main ioctl to access SEV is KVM_MEMORY_ENCRYPT_OP. If the argument to KVM_MEMORY_ENCRYPT_OP is NULL, the ioctl returns 0 if SEV is enabled @@ -87,10 +81,6 @@ guests, such as launching, running, snapshotting, migrating and decommissioning. The KVM_SEV_INIT command is used by the hypervisor to initialize the SEV platform context. In a typical workflow, this command should be the first command issued. -The firmware can be initialized either by using its own non-volatile storage or -the OS can manage the NV storage for the firmware using the module parameter -``init_ex_path``. If the file specified by ``init_ex_path`` does not exist or -is invalid, the OS will create or override the file with output from PSP. Returns: 0 on success, -negative on error @@ -434,6 +424,21 @@ issued by the hypervisor to make the guest ready for execution. Returns: 0 on success, -negative on error +Firmware Management +=================== + +The SEV guest key management is handled by a separate processor called the AMD +Secure Processor (AMD-SP). Firmware running inside the AMD-SP provides a secure +key management interface to perform common hypervisor activities such as +encrypting bootstrap code, snapshot, migrating and debugging the guest. For more +information, see the SEV Key Management spec [api-spec]_ + +The AMD-SP firmware can be initialized either by using its own non-volatile +storage or the OS can manage the NV storage for the firmware using +parameter ``init_ex_path`` of the ``ccp`` module. If the file specified +by ``init_ex_path`` does not exist or is invalid, the OS will create or +override the file with PSP non-volatile storage. + References ==========