public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Gonda <pgonda@google.com>
Subject: [PATCH 0/2] KVM: SVM: Fix SEV-ES intrahost migration
Date: Thu, 24 Aug 2023 19:23:55 -0700	[thread overview]
Message-ID: <20230825022357.2852133-1-seanjc@google.com> (raw)

Fix two fatal bugs in SEV-ES intrahost migration, found by running
sev_migrate_tests (:shocked-pikachu:).

IIRC, for some reason our platforms haven't played nice with SEV-ES on
upstream kernels for a while, i.e. the test hasn't been run as part of my
usual testing. 

Sean Christopherson (2):
  KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost
    migration
  KVM: SVM: Skip VMSA init in sev_es_init_vmcb() if pointer is NULL

 arch/x86/kvm/svm/sev.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)


base-commit: fff2e47e6c3b8050ca26656693caa857e3a8b740
-- 
2.42.0.rc2.253.gd59a3bf2b4-goog


             reply	other threads:[~2023-08-25  2:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  2:23 Sean Christopherson [this message]
2023-08-25  2:23 ` [PATCH 1/2] KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration Sean Christopherson
2023-08-25 10:23   ` Gupta, Pankaj
2023-08-25 13:54     ` Peter Gonda
2023-08-25  2:23 ` [PATCH 2/2] KVM: SVM: Skip VMSA init in sev_es_init_vmcb() if pointer is NULL Sean Christopherson
2023-08-25 10:26   ` Gupta, Pankaj
2023-08-25 13:56     ` Peter Gonda
2023-08-25 19:02 ` [PATCH 0/2] KVM: SVM: Fix SEV-ES intrahost migration 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=20230825022357.2852133-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pgonda@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