From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Steve Rutherford <srutherford@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>, Joerg Roedel <joro@8bytes.org>,
Brijesh Singh <brijesh.singh@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Venu Busireddy <venu.busireddy@oracle.com>
Subject: Re: [PATCH v2 2/2] KVM: x86: add MSR_KVM_MIGRATION_CONTROL
Date: Thu, 29 Apr 2021 12:09:16 +0200 [thread overview]
Message-ID: <cc0c6333-6c2f-e8f3-f838-3cb2492f007a@redhat.com> (raw)
In-Reply-To: <YInAT6MYU2N0tKSW@google.com>
On 28/04/21 22:06, Sean Christopherson wrote:
> But there's only multiple meanings if we define the bit to be specific to
> page encryption. E.g. if the bit is KVM_READY_FOR_MIGRATION, then its meaning
> (when cleared) is simply "please don't migrate me, I will die". KVM doesn't
> care_why_ the guest is telling userspace that it's not ready for migration, nor
> does KVM care if userspace honors the indicator.
Makes sense, I'll change that.
Paolo
prev parent reply other threads:[~2021-04-29 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 17:37 [PATCH v2 0/2] KVM: x86: guest interface for SEV live migration Paolo Bonzini
2021-04-21 17:37 ` [PATCH v2 1/2] KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall Paolo Bonzini
2021-04-27 22:04 ` Sean Christopherson
2021-04-21 17:37 ` [PATCH v2 2/2] KVM: x86: add MSR_KVM_MIGRATION_CONTROL Paolo Bonzini
2021-04-27 22:14 ` Sean Christopherson
2021-04-28 19:56 ` Steve Rutherford
2021-04-28 20:06 ` Sean Christopherson
2021-04-29 10:09 ` Paolo Bonzini [this message]
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=cc0c6333-6c2f-e8f3-f838-3cb2492f007a@redhat.com \
--to=pbonzini@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=srutherford@google.com \
--cc=thomas.lendacky@amd.com \
--cc=venu.busireddy@oracle.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
all inboxes | Powered by JetHome®