[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libvir-list
Subject:    Re: [PATCH v2 0/1] Expose availability of SEV-ES
From:       Takashi Kajinami <kajinamit () oss ! nttdata ! com>
Date:       2024-03-28 7:35:19
Message-ID: b52ced86-2702-4e4a-8830-98f5c017e9e0 () oss ! nttdata ! com
[Download RAW message or body]

I wonder if I can hear any feedback about the change.
# This is my first time to propose a change to libvirt and I appreciate
# any comments in case I made something wrong.

On 2/20/24 15:31, Takashi Kajinami wrote:
> This introduces the new "model" field in sev elements so that clients can
> check whether SEV-ES, the 2nd generation of AMD SEV, is available in
> the taget hyprvisor. There is the maxESGuests field (along with the maxGuests
> field) but this field does not explain whether SEV-ES is actually
> enabled in KVM.
> 
> Takashi Kajinami (1):
>    Expose available AMD SEV models in domain capabilities
> 
> Changes since v1:
>    * Fixed one code path where available models are not added
>    * Fixed missing update of "report" flag
>    * Updated the documentation to explain the new model field in addition
>      to the existing but undocumanted cpu0Id field
> 
> Takashi Kajinami (1):
>    Expose available AMD SEV models in domain capabilities
> 
>   docs/formatdomaincaps.rst      |  5 ++
>   src/conf/domain_capabilities.c |  2 +
>   src/conf/domain_capabilities.h |  1 +
>   src/conf/domain_conf.c         |  7 +++
>   src/conf/domain_conf.h         |  8 ++++
>   src/qemu/qemu_capabilities.c   | 84 +++++++++++++++++++++++++---------
>   6 files changed, 85 insertions(+), 22 deletions(-)
> 
_______________________________________________
Devel mailing list -- devel@lists.libvirt.org
To unsubscribe send an email to devel-leave@lists.libvirt.org

[prev in list] [next in list] [prev in thread] [next in thread]