all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>,
	pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH qemu-server v2 2/2] config: add AMD SEV-SNP support.
Date: Tue, 18 Feb 2025 12:00:32 +0100	[thread overview]
Message-ID: <fede184f-f5eb-4138-a163-6614b7c21629@proxmox.com> (raw)
In-Reply-To: <20250217140705.271726-5-philipp.giersfeld@canarybit.eu>

On 2/17/25 15:06, Philipp Giersfeld wrote:
> This patch is for enabling AMD SEV-SNP support.
> 
> Where applicable, it extends support for existing SEV(-ES) variables
> to SEV-SNP. This means that it retains no-debug and kernel-hashes
> options, but the no-key-sharing option is removed.
> 
> The default policy value is identical to QEMU’s, and the therefore
> required option has been added to configure SMT support.
> 
> The code was tested by running a VM without SEV, with SEV, SEV-ES,
> SEV-SNP. Each configuration was tested with and without an EFI disk
> attached. For SEV-enabled configurations it was also verified that the
> kernel actually used the respective feature.
> 
> Signed-off-by: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
> Reviewed-by: Daniel Kral <d.kral at proxmox.com>
> ---
> 
>   changes since v1: https://lists.proxmox.com/pipermail/pve-devel/2025-February/068159.html
>   * Fix formatting and code layout
>   * Fix bug in policy calculation
> 
> Signed-off-by: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>

LGTM! As already pointed out by @Markus in another patch, the Signed-off 
is only needed for the patch message itself, not the comments, but no 
trouble at all - it's not relevant when applied anyway.

Cross-checked with my nits & comments and all were implemented, so it's 
indeed:

Reviewed-by: Daniel Kral <d.kral@proxmox.com>

BTW is there a reason you used the at form at the tested-by/reviewed-by 
emails?


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-02-18 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 14:06 [pve-devel] [PATCH edk2-firmware/qemu-server/manager 0/5] AMD SEV-SNP Philipp Giersfeld
2025-02-17 14:06 ` [pve-devel] [PATCH edk2-firmware v2 1/2] Update edk2 to edkstable202411 Philipp Giersfeld
2025-02-17 14:06 ` [pve-devel] [PATCH edk2-firmware v2 2/2] Add OVMF targets for AMD SEV-ES and SEV-SNP Philipp Giersfeld
2025-02-17 14:06 ` [pve-devel] [PATCH qemu-server v2 1/2] Convert policy calculation Philipp Giersfeld
2025-02-18 10:56   ` Daniel Kral
2025-02-17 14:06 ` [pve-devel] [PATCH qemu-server v2 2/2] config: add AMD SEV-SNP support Philipp Giersfeld
2025-02-18 11:00   ` Daniel Kral [this message]
2025-02-17 14:06 ` [pve-devel] [PATCH pve-manager v2 1/1] Add configuration options for AMD SEV-SNP Philipp Giersfeld
2025-02-18  9:19   ` Markus Frank

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=fede184f-f5eb-4138-a163-6614b7c21629@proxmox.com \
    --to=d.kral@proxmox.com \
    --cc=philipp.giersfeld@canarybit.eu \
    --cc=pve-devel@lists.proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal