qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Roy Hopkins <roy.hopkins@randomman.co.uk>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P . Berrange" <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>, Igor Mammedov <imammedo@redhat.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Michael Roth <michael.roth@amd.com>,
	Ani Sinha <anisinha@redhat.com>, Joerg Roedel <jroedel@suse.com>
Subject: Re: [PATCH v7 03/16] backends/igvm: Add IGVM loader and configuration
Date: Mon, 3 Mar 2025 10:03:41 +0100	[thread overview]
Message-ID: <7fd33c84-191f-43cc-a513-f0f762026b11@redhat.com> (raw)
In-Reply-To: <928b7178f2960441871dbb8145f639b10ac84ccb.1740663410.git.roy.hopkins@randomman.co.uk>

On 27.02.25 14:44, Roy Hopkins wrote:
> Adds an IGVM loader to QEMU which processes a given IGVM file and
> applies the directives within the file to the current guest
> configuration.
> 
> The IGVM loader can be used to configure both confidential and
> non-confidential guests. For confidential guests, the
> ConfidentialGuestSupport object for the system is used to encrypt
> memory, apply the initial CPU state and perform other confidential guest
> operations.
> 
> The loader is configured via a new IgvmCfg QOM object which allows the
> user to provide a path to the IGVM file to process.
> 
> Signed-off-by: Roy Hopkins <roy.hopkins@randomman.co.uk>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
>   backends/igvm-cfg.c       |  52 +++
>   backends/igvm.c           | 808 ++++++++++++++++++++++++++++++++++++++
>   backends/igvm.h           |  23 ++

Just a general comment that could also be considered at a later point, 
after this was moved: Is "backends" really the right directory, and if 
so, would it make sense to start adding sub-directories? For example, 
all "hostmem" stuff could be moved into a subdirectory.

Would an "igvm" directory also be the right place for 
backends/confidential-guest-support.c, or would we be looking for 
something more abstract?

-- 
Cheers,

David / dhildenb



  parent reply	other threads:[~2025-03-03  9:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 13:38 [PATCH v7 00/16] Introduce support for IGVM files Roy Hopkins
2025-02-27 13:38 ` [PATCH v7 01/16] meson: Add optional dependency on IGVM library Roy Hopkins
2025-02-27 13:44 ` [PATCH v7 02/16] backends/confidential-guest-support: Add functions to support IGVM Roy Hopkins
2025-02-27 13:44 ` [PATCH v7 03/16] backends/igvm: Add IGVM loader and configuration Roy Hopkins
2025-02-28 13:13   ` Gerd Hoffmann
2025-06-13 10:54     ` Roy Hopkins
2025-03-03  9:03   ` David Hildenbrand [this message]
2025-02-27 13:49 ` [PATCH v7 04/16] hw/i386: Add igvm-cfg object and processing for IGVM files Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 05/16] i386/pc_sysfw: Ensure sysfw flash configuration does not conflict with IGVM Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 06/16] sev: Update launch_update_data functions to use Error handling Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 07/16] target/i386: Allow setting of R_LDTR and R_TR with cpu_x86_load_seg_cache() Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 08/16] i386/sev: Refactor setting of reset vector and initial CPU state Roy Hopkins
2025-02-27 17:06   ` Gupta, Pankaj
2025-02-27 14:29 ` [PATCH v7 09/16] i386/sev: Implement ConfidentialGuestSupport functions for SEV Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 10/16] docs/system: Add documentation on support for IGVM Roy Hopkins
2025-02-27 17:12   ` Gupta, Pankaj
2025-02-27 14:29 ` [PATCH v7 11/16] docs/interop/firmware.json: Add igvm to FirmwareDevice Roy Hopkins
2025-02-28 13:15   ` Gerd Hoffmann
2025-02-27 14:29 ` [PATCH v7 12/16] backends/confidential-guest-support: Add set_guest_policy() function Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 13/16] backends/igvm: Process initialization sections in IGVM file Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 14/16] backends/igvm: Handle policy for SEV guests Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 15/16] i386/sev: Add implementation of CGS set_guest_policy() Roy Hopkins
2025-02-27 14:29 ` [PATCH v7 16/16] sev: Provide sev_features flags from IGVM VMSA to KVM_SEV_INIT2 Roy Hopkins
2025-02-27 15:32 ` [PATCH v7 00/16] Introduce support for IGVM files Stefano Garzarella
2025-02-27 16:12   ` Roy Hopkins
2025-02-28  9:26     ` Stefano Garzarella
2025-02-27 15:35 ` [PATCH v7 16/16] sev: Provide sev_features flags from IGVM VMSA to KVM_SEV_INIT2 Roy Hopkins
2025-02-27 15:47 ` Roy Hopkins
2025-02-27 15:56 ` Roy Hopkins
2025-02-28 13:18 ` [PATCH v7 00/16] Introduce support for IGVM files Gerd Hoffmann
2025-03-05 15:47 ` Stefano Garzarella
2025-03-06 11:48   ` Roy Hopkins
2025-03-06 13:09     ` Stefano Garzarella
2025-05-20 10:01 ` Ani Sinha
     [not found] ` <b43aa3fa.AUoAAGOlyUYAAAAAAAAAA9cBm3AAAYKJZwAAAAAAAC5ATwBnwHdy@mailjet.com>
2025-06-12 12:03   ` [PATCH v7 08/16] i386/sev: Refactor setting of reset vector and initial CPU state Ani Sinha
2025-06-16  8:39     ` Ani Sinha
     [not found] ` <ec4fb8e4.AUUAAGN5T_UAAAAAAAAAA9cBm3AAAYKJZwAAAAAAAC5ATwBnwULW@mailjet.com>
2025-06-13 12:11   ` [PATCH v7 15/16] i386/sev: Add implementation of CGS set_guest_policy() Ani Sinha
2025-06-13 12:20     ` 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=7fd33c84-191f-43cc-a513-f0f762026b11@redhat.com \
    --to=david@redhat.com \
    --cc=alistair@alistair23.me \
    --cc=anisinha@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@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@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).