From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Roy Hopkins <roy.hopkins@randomman.co.uk>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@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>, Gerd Hoffman <kraxel@redhat.com>,
Pankaj Gupta <pankaj.gupta@amd.com>,
Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH v9 00/16] Introduce support for IGVM files
Date: Tue, 8 Jul 2025 16:32:34 +0100 [thread overview]
Message-ID: <aG06EnbOg3a--2jl@redhat.com> (raw)
In-Reply-To: <cover.1751554099.git.roy.hopkins@randomman.co.uk>
On Thu, Jul 03, 2025 at 03:59:33PM +0100, Roy Hopkins wrote:
> Here is v9 of the set of patches to add support for IGVM files to QEMU. This is
> based on commit c77283dd5d79149f4e7e9edd00f65416c648ee59 of qemu.
>
> Once again, this is mostly a rebase of the previous patch series. However,
> thanks to those reviewers who have provided feedback on v8 which has now been
> addressed in this new version.
>
> This v9 patch series is also available on github: [2]
>
> For testing IGVM support in QEMU you need to generate an IGVM file that is
> configured for the platform you want to launch. You can use the `buildigvm`
> test tool [3] to allow generation of IGVM files for all currently supported
> platforms. Patch 11/17 contains information on how to generate an IGVM file
> using this tool.
>
> Changes in v9:
>
> * Address review comments from v8
> * Add metadata to relevant commits.
>
> Patch summary:
>
> 1-11: Add support and documentation for processing IGVM files for SEV, SEV-ES,
> SEV-SNP and native platforms.
>
> 12-15: Processing of policy and SEV-SNP ID_BLOCK from IGVM file.
>
> 16: Add pre-processing of IGVM file to support synchronization of 'SEV_FEATURES'
> from IGVM VMSA to KVM.
IIRC, way back in the early draft of this you have included some pieces
related to TDX which we then dropped since TDX wasn't ready in QEMU
upstream.
Now that TDX merged in QEMU a few weeks back, I'm wondering what gaps there
are in this series wrt TDX support ?
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-07-08 20:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 14:59 [PATCH v9 00/16] Introduce support for IGVM files Roy Hopkins
2025-07-03 15:00 ` [PATCH v9 01/16] meson: Add optional dependency on IGVM library Roy Hopkins
2025-07-03 15:03 ` [PATCH v9 02/16] backends/confidential-guest-support: Add functions to support IGVM Roy Hopkins
2025-07-08 15:07 ` Daniel P. Berrangé
2025-07-11 5:47 ` Ani Sinha
2025-07-03 15:10 ` [PATCH v9 03/16] backends/igvm: Add IGVM loader and configuration Roy Hopkins
2025-07-03 15:11 ` [PATCH v9 04/16] hw/i386: Add igvm-cfg object and processing for IGVM files Roy Hopkins
2025-07-03 15:15 ` [PATCH v9 05/16] i386/pc_sysfw: Ensure sysfw flash configuration does not conflict with IGVM Roy Hopkins
2025-07-03 15:21 ` [PATCH v9 06/16] sev: Update launch_update_data functions to use Error handling Roy Hopkins
2025-07-03 15:31 ` [PATCH v9 07/16] target/i386: Allow setting of R_LDTR and R_TR with cpu_x86_load_seg_cache() Roy Hopkins
2025-07-03 15:31 ` [PATCH v9 08/16] i386/sev: Refactor setting of reset vector and initial CPU state Roy Hopkins
2025-07-08 15:25 ` Daniel P. Berrangé
2025-07-08 15:28 ` Daniel P. Berrangé
2025-07-03 15:34 ` [PATCH v9 09/16] i386/sev: Implement ConfidentialGuestSupport functions for SEV Roy Hopkins
2025-07-03 15:41 ` [PATCH v9 10/16] docs/system: Add documentation on support for IGVM Roy Hopkins
2025-07-03 16:02 ` [PATCH v9 11/16] docs/interop/firmware.json: Add igvm to FirmwareDevice Roy Hopkins
2025-07-03 16:02 ` [PATCH v9 12/16] backends/confidential-guest-support: Add set_guest_policy() function Roy Hopkins
2025-07-03 16:18 ` [PATCH v9 13/16] backends/igvm: Process initialization sections in IGVM file Roy Hopkins
2025-07-03 16:21 ` [PATCH v9 14/16] backends/igvm: Handle policy for SEV guests Roy Hopkins
2025-07-03 16:21 ` [PATCH v9 15/16] i386/sev: Add implementation of CGS set_guest_policy() Roy Hopkins
2025-07-03 16:21 ` [PATCH v9 16/16] sev: Provide sev_features flags from IGVM VMSA to KVM_SEV_INIT2 Roy Hopkins
2025-07-08 13:28 ` [PATCH v9 00/16] Introduce support for IGVM files Stefano Garzarella
2025-07-08 15:32 ` Daniel P. Berrangé [this message]
2025-07-08 17:11 ` Paolo Bonzini
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=aG06EnbOg3a--2jl@redhat.com \
--to=berrange@redhat.com \
--cc=alistair@alistair23.me \
--cc=anisinha@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=joro@8bytes.org \
--cc=kraxel@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pankaj.gupta@amd.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roy.hopkins@randomman.co.uk \
--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).