From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: qemu-devel@nongnu.org,
Alistair Francis <alistair.francis@xilinx.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Eric Blake <eblake@redhat.com>,
kvm@vger.kernel.org, Marcel Apfelbaum <marcel@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <richard.henderson@linaro.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
Thomas Lendacky <Thomas.Lendacky@amd.com>,
Borislav Petkov <bp@suse.de>, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v7 17/26] target/i386: encrypt bios rom
Date: Fri, 9 Feb 2018 18:28:20 +0000 [thread overview]
Message-ID: <20180209182819.GH2428@work-vm> (raw)
In-Reply-To: <20180207160638.98872-17-brijesh.singh@amd.com>
* Brijesh Singh (brijesh.singh@amd.com) wrote:
> SEV requires that guest bios must be encrypted before booting the guest.
I'm curious; is it just the main BIOS that needs encryption - what about
things like device/PXE rom images?
Dave
>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Richard Henderson <rth@twiddle.net>
> Cc: Eduardo Habkost <ehabkost@redhat.com>
> Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
> ---
> hw/i386/pc_sysfw.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/hw/i386/pc_sysfw.c b/hw/i386/pc_sysfw.c
> index 6b183747fcea..8ddbbf74d330 100644
> --- a/hw/i386/pc_sysfw.c
> +++ b/hw/i386/pc_sysfw.c
> @@ -112,6 +112,8 @@ static void pc_system_flash_init(MemoryRegion *rom_memory)
> pflash_t *system_flash;
> MemoryRegion *flash_mem;
> char name[64];
> + void *flash_ptr;
> + int ret, flash_size;
>
> sector_bits = 12;
> sector_size = 1 << sector_bits;
> @@ -168,6 +170,17 @@ static void pc_system_flash_init(MemoryRegion *rom_memory)
> if (unit == 0) {
> flash_mem = pflash_cfi01_get_memory(system_flash);
> pc_isa_bios_init(rom_memory, flash_mem, size);
> +
> + /* Encrypt the pflash boot ROM */
> + if (kvm_memcrypt_enabled()) {
> + flash_ptr = memory_region_get_ram_ptr(flash_mem);
> + flash_size = memory_region_size(flash_mem);
> + ret = kvm_memcrypt_encrypt_data(flash_ptr, flash_size);
> + if (ret) {
> + error_report("failed to encrypt pflash rom");
> + exit(1);
> + }
> + }
> }
> }
> }
> --
> 2.14.3
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-02-09 18:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 16:06 [Qemu-devel] [PATCH v7 01/26] memattrs: add debug attribute Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 02/26] exec: add ram_debug_ops support Brijesh Singh
2018-02-07 16:19 ` Eric Blake
2018-02-07 16:33 ` Brijesh Singh
2018-02-07 16:46 ` Eric Blake
2018-02-07 16:51 ` Paolo Bonzini
2018-02-07 20:26 ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 03/26] exec: add debug version of physical memory read and write API Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 04/26] monitor/i386: use debug APIs when accessing guest memory Brijesh Singh
2018-02-07 16:53 ` Paolo Bonzini
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 05/26] target/i386: add memory encryption feature cpuid support Brijesh Singh
2018-02-07 16:54 ` Paolo Bonzini
2018-02-07 18:28 ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 06/26] machine: add -memory-encryption property Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 07/26] kvm: update kvm.h to include memory encryption ioctls Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 08/26] docs: add AMD Secure Encrypted Virtualization (SEV) Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 09/26] accel: add Secure Encrypted Virtulization (SEV) object Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 10/26] sev: add command to initialize the memory encryption context Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 11/26] sev: register the guest memory range which may contain encrypted data Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 12/26] kvm: introduce memory encryption APIs Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 13/26] qmp: add query-sev command Brijesh Singh
2018-02-07 16:22 ` Eric Blake
2018-02-07 16:36 ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 14/26] hmp: add 'info sev' command Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 15/26] sev: add command to create launch memory encryption context Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 16/26] sev: add command to encrypt guest memory region Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 17/26] target/i386: encrypt bios rom Brijesh Singh
2018-02-09 18:28 ` Dr. David Alan Gilbert [this message]
2018-02-09 20:49 ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 18/26] sev: add support to LAUNCH_MEASURE command Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 19/26] sev: Finalize the SEV guest launch flow Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 20/26] hw: i386: set ram_debug_ops when memory encryption is enabled Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 21/26] sev: add debug encrypt and decrypt commands Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 22/26] target/i386: clear C-bit when walking SEV guest page table Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 23/26] include: add psp-sev.h header file Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 25/26] sev: add support to KVM_SEV_GUEST_STATUS Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 26/26] qmp: add query-sev-launch-measure command Brijesh Singh
2018-02-07 16:29 ` Eric Blake
2018-02-07 18:12 ` Brijesh Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180209182819.GH2428@work-vm \
--to=dgilbert@redhat.com \
--cc=Thomas.Lendacky@amd.com \
--cc=alistair.francis@xilinx.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=cornelia.huck@de.ibm.com \
--cc=crosthwaite.peter@gmail.com \
--cc=eblake@redhat.com \
--cc=edgar.iglesias@xilinx.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).