From: "Gupta, Pankaj" <pankaj.gupta@amd.com>
To: Roy Hopkins <roy.hopkins@suse.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Sergio Lopez" <slp@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Alistair Francis" <alistair@alistair23.me>,
"Peter Xu" <peterx@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
"Michael Roth" <michael.roth@amd.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Jörg Roedel" <jroedel@suse.com>
Subject: Re: [PATCH v6 05/16] i386/pc_sysfw: Ensure sysfw flash configuration does not conflict with IGVM
Date: Mon, 7 Oct 2024 20:53:58 +0200 [thread overview]
Message-ID: <78028d69-90c8-a295-9393-1f6d6c3826cc@amd.com> (raw)
In-Reply-To: <3255767a6d34297ec47f43f9ae9434116d3f17ba.1727341768.git.roy.hopkins@suse.com>
> When using an IGVM file the configuration of the system firmware is
> defined by IGVM directives contained in the file. In this case the user
> should not configure any pflash devices.
>
> This commit skips initialization of the ROM mode when pflash0 is not set
> then checks to ensure no pflash devices have been configured when using
> IGVM, exiting with an error message if this is not the case.
>
> Signed-off-by: Roy Hopkins <roy.hopkins@suse.com>
Reviewed-by: Pankaj Gupta <pankaj.gupta@amd.com>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
> hw/i386/pc_sysfw.c | 31 ++++++++++++++++++++++++++++---
> 1 file changed, 28 insertions(+), 3 deletions(-)
>
> diff --git a/hw/i386/pc_sysfw.c b/hw/i386/pc_sysfw.c
> index ef80281d28..f5e40b3ef6 100644
> --- a/hw/i386/pc_sysfw.c
> +++ b/hw/i386/pc_sysfw.c
> @@ -219,7 +219,13 @@ void pc_system_firmware_init(PCMachineState *pcms,
> BlockBackend *pflash_blk[ARRAY_SIZE(pcms->flash)];
>
> if (!pcmc->pci_enabled) {
> - x86_bios_rom_init(X86_MACHINE(pcms), "bios.bin", rom_memory, true);
> + /*
> + * If an IGVM file is specified then the firmware must be provided
> + * in the IGVM file.
> + */
> + if (!X86_MACHINE(pcms)->igvm) {
> + x86_bios_rom_init(X86_MACHINE(pcms), "bios.bin", rom_memory, true);
> + }
> return;
> }
>
> @@ -239,8 +245,13 @@ void pc_system_firmware_init(PCMachineState *pcms,
> }
>
> if (!pflash_blk[0]) {
> - /* Machine property pflash0 not set, use ROM mode */
> - x86_bios_rom_init(X86_MACHINE(pcms), "bios.bin", rom_memory, false);
> + /*
> + * Machine property pflash0 not set, use ROM mode unless using IGVM,
> + * in which case the firmware must be provided by the IGVM file.
> + */
> + if (!X86_MACHINE(pcms)->igvm) {
> + x86_bios_rom_init(X86_MACHINE(pcms), "bios.bin", rom_memory, false);
> + }
> } else {
> if (kvm_enabled() && !kvm_readonly_mem_enabled()) {
> /*
> @@ -256,6 +267,20 @@ void pc_system_firmware_init(PCMachineState *pcms,
> }
>
> pc_system_flash_cleanup_unused(pcms);
> +
> + /*
> + * The user should not have specified any pflash devices when using IGVM
> + * to configure the guest.
> + */
> + if (X86_MACHINE(pcms)->igvm) {
> + for (i = 0; i < ARRAY_SIZE(pcms->flash); i++) {
> + if (pcms->flash[i]) {
> + error_report("pflash devices cannot be configured when "
> + "using IGVM");
> + exit(1);
> + }
> + }
> + }
> }
>
> void x86_firmware_configure(hwaddr gpa, void *ptr, int size)
next prev parent reply other threads:[~2024-10-07 19:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 11:41 [PATCH v6 00/16] Introduce support for IGVM files Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 01/16] meson: Add optional dependency on IGVM library Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 02/16] backends/confidential-guest-support: Add functions to support IGVM Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 03/16] backends/igvm: Add IGVM loader and configuration Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 04/16] hw/i386: Add igvm-cfg object and processing for IGVM files Roy Hopkins
2024-10-01 9:53 ` Stefano Garzarella
2024-10-22 9:04 ` Stefano Garzarella
2024-09-26 11:41 ` [PATCH v6 05/16] i386/pc_sysfw: Ensure sysfw flash configuration does not conflict with IGVM Roy Hopkins
2024-10-07 18:53 ` Gupta, Pankaj [this message]
2024-09-26 11:41 ` [PATCH v6 06/16] sev: Update launch_update_data functions to use Error handling Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 07/16] target/i386: Allow setting of R_LDTR and R_TR with cpu_x86_load_seg_cache() Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 08/16] i386/sev: Refactor setting of reset vector and initial CPU state Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 09/16] i386/sev: Implement ConfidentialGuestSupport functions for SEV Roy Hopkins
2024-09-26 11:41 ` [PATCH v6 10/16] docs/system: Add documentation on support for IGVM Roy Hopkins
2024-09-26 11:42 ` [PATCH v6 11/16] docs/interop/firmware.json: Add igvm to FirmwareDevice Roy Hopkins
2024-09-26 11:42 ` [PATCH v6 12/16] backends/confidential-guest-support: Add set_guest_policy() function Roy Hopkins
2024-09-26 11:42 ` [PATCH v6 13/16] backends/igvm: Process initialization sections in IGVM file Roy Hopkins
2024-09-26 11:42 ` [PATCH v6 14/16] backends/igvm: Handle policy for SEV guests Roy Hopkins
2024-09-26 11:42 ` [PATCH v6 15/16] i386/sev: Add implementation of CGS set_guest_policy() Roy Hopkins
2024-09-26 11:42 ` [PATCH v6 16/16] sev: Provide sev_features flags from IGVM VMSA to KVM_SEV_INIT2 Roy Hopkins
2024-10-21 14:44 ` [PATCH v6 00/16] Introduce support for IGVM files Roy Hopkins
2024-10-22 9:05 ` Stefano Garzarella
2024-10-22 11:31 ` Roy Hopkins
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=78028d69-90c8-a295-9393-1f6d6c3826cc@amd.com \
--to=pankaj.gupta@amd.com \
--cc=alistair@alistair23.me \
--cc=anisinha@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=jroedel@suse.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roy.hopkins@suse.com \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.com \
--cc=thomas.lendacky@amd.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).