From: Michael Roth <michael.roth@amd.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<seanjc@google.com>, <aik@amd.com>, <isaku.yamahata@intel.com>
Subject: Re: [PATCH 01/10] KVM: SEV: fix compat ABI for KVM_MEMORY_ENCRYPT_OP
Date: Wed, 14 Feb 2024 16:50:41 -0600 [thread overview]
Message-ID: <20240214225041.lmlgchx76eapcx2o@amd.com> (raw)
In-Reply-To: <20240209183743.22030-2-pbonzini@redhat.com>
On Fri, Feb 09, 2024 at 01:37:33PM -0500, Paolo Bonzini wrote:
> The data structs for KVM_MEMORY_ENCRYPT_OP have different sizes for 32- and 64-bit
> kernels, but they do not make any attempt to convert from one ABI to the other.
> Fix this by adding the appropriate padding.
>
> No functional change intended for 64-bit userspace.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Michael Roth <michael.roth@amd.com>
> ---
> arch/x86/include/uapi/asm/kvm.h | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/arch/x86/include/uapi/asm/kvm.h b/arch/x86/include/uapi/asm/kvm.h
> index 0ad6bda1fc39..b305daff056e 100644
> --- a/arch/x86/include/uapi/asm/kvm.h
> +++ b/arch/x86/include/uapi/asm/kvm.h
> @@ -687,6 +687,7 @@ enum sev_cmd_id {
>
> struct kvm_sev_cmd {
> __u32 id;
> + __u32 pad0;
> __u64 data;
> __u32 error;
> __u32 sev_fd;
> @@ -697,28 +698,35 @@ struct kvm_sev_launch_start {
> __u32 policy;
> __u64 dh_uaddr;
> __u32 dh_len;
> + __u32 pad0;
> __u64 session_uaddr;
> __u32 session_len;
> + __u32 pad1;
> };
>
> struct kvm_sev_launch_update_data {
> __u64 uaddr;
> __u32 len;
> + __u32 pad0;
> };
>
>
> struct kvm_sev_launch_secret {
> __u64 hdr_uaddr;
> __u32 hdr_len;
> + __u32 pad0;
> __u64 guest_uaddr;
> __u32 guest_len;
> + __u32 pad1;
> __u64 trans_uaddr;
> __u32 trans_len;
> + __u32 pad2;
> };
>
> struct kvm_sev_launch_measure {
> __u64 uaddr;
> __u32 len;
> + __u32 pad0;
> };
>
> struct kvm_sev_guest_status {
> @@ -731,33 +739,43 @@ struct kvm_sev_dbg {
> __u64 src_uaddr;
> __u64 dst_uaddr;
> __u32 len;
> + __u32 pad0;
> };
>
> struct kvm_sev_attestation_report {
> __u8 mnonce[16];
> __u64 uaddr;
> __u32 len;
> + __u32 pad0;
> };
>
> struct kvm_sev_send_start {
> __u32 policy;
> + __u32 pad0;
> __u64 pdh_cert_uaddr;
> __u32 pdh_cert_len;
> + __u32 pad1;
> __u64 plat_certs_uaddr;
> __u32 plat_certs_len;
> + __u32 pad2;
> __u64 amd_certs_uaddr;
> __u32 amd_certs_len;
> + __u32 pad3;
> __u64 session_uaddr;
> __u32 session_len;
> + __u32 pad4;
> };
>
> struct kvm_sev_send_update_data {
> __u64 hdr_uaddr;
> __u32 hdr_len;
> + __u32 pad0;
> __u64 guest_uaddr;
> __u32 guest_len;
> + __u32 pad1;
> __u64 trans_uaddr;
> __u32 trans_len;
> + __u32 pad2;
> };
>
> struct kvm_sev_receive_start {
> @@ -765,17 +783,22 @@ struct kvm_sev_receive_start {
> __u32 policy;
> __u64 pdh_uaddr;
> __u32 pdh_len;
> + __u32 pad0;
> __u64 session_uaddr;
> __u32 session_len;
> + __u32 pad1;
> };
>
> struct kvm_sev_receive_update_data {
> __u64 hdr_uaddr;
> __u32 hdr_len;
> + __u32 pad0;
> __u64 guest_uaddr;
> __u32 guest_len;
> + __u32 pad1;
> __u64 trans_uaddr;
> __u32 trans_len;
> + __u32 pad2;
> };
>
> #define KVM_X2APIC_API_USE_32BIT_IDS (1ULL << 0)
> --
> 2.39.0
>
>
next prev parent reply other threads:[~2024-02-15 1:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 18:37 [PATCH 00/10] KVM: SEV: allow customizing VMSA features Paolo Bonzini
2024-02-09 18:37 ` [PATCH 01/10] KVM: SEV: fix compat ABI for KVM_MEMORY_ENCRYPT_OP Paolo Bonzini
2024-02-14 22:50 ` Michael Roth [this message]
2024-02-09 18:37 ` [PATCH 02/10] KVM: introduce new vendor op for KVM_GET_DEVICE_ATTR Paolo Bonzini
2024-02-14 22:57 ` Michael Roth
2024-02-09 18:37 ` [PATCH 03/10] Documentation: kvm/sev: separate description of firmware Paolo Bonzini
2024-02-14 23:23 ` Michael Roth
2024-02-09 18:37 ` [PATCH 04/10] KVM: SEV: publish supported VMSA features Paolo Bonzini
2024-02-14 23:49 ` Michael Roth
2024-02-09 18:37 ` [PATCH 05/10] KVM: SEV: store VMSA features in kvm_sev_info Paolo Bonzini
2024-02-15 0:03 ` Michael Roth
2024-02-09 18:37 ` [PATCH 06/10] KVM: x86: define standard behavior for bits 0/1 of VM type Paolo Bonzini
2024-02-09 18:37 ` [PATCH 07/10] KVM: x86: Add is_vm_type_supported callback Paolo Bonzini
2024-02-15 0:33 ` Michael Roth
2024-02-15 13:35 ` Paolo Bonzini
2024-02-09 18:37 ` [PATCH 08/10] KVM: SEV: define VM types for SEV and SEV-ES Paolo Bonzini
2024-02-15 1:19 ` Michael Roth
2024-02-15 13:40 ` Paolo Bonzini
2024-02-09 18:37 ` [PATCH 09/10] KVM: SEV: introduce KVM_SEV_INIT2 operation Paolo Bonzini
2024-02-15 1:34 ` Michael Roth
2024-02-15 13:44 ` Paolo Bonzini
2024-02-15 14:44 ` Michael Roth
2024-02-15 17:28 ` Paolo Bonzini
2024-02-15 17:54 ` Michael Roth
2024-02-15 18:08 ` Paolo Bonzini
2024-02-15 20:44 ` Michael Roth
2024-02-15 11:07 ` Alexey Kardashevskiy
2024-02-15 21:14 ` Tom Lendacky
2024-02-09 18:37 ` [PATCH 10/10] selftests: kvm: add tests for KVM_SEV_INIT2 Paolo Bonzini
2024-02-09 18:37 ` [PATCH 11/10] selftests: kvm: switch sev_migrate_tests to KVM_SEV_INIT2 Paolo Bonzini
2024-02-09 19:40 ` [PATCH 00/10] KVM: SEV: allow customizing VMSA features Sean Christopherson
2024-02-09 22:40 ` Paolo Bonzini
2024-02-13 2:46 ` Sean Christopherson
2024-02-13 14:44 ` Paolo Bonzini
2024-02-17 1:40 ` Sean Christopherson
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=20240214225041.lmlgchx76eapcx2o@amd.com \
--to=michael.roth@amd.com \
--cc=aik@amd.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
Powered by JetHome