From: Brijesh Singh <brijesh.singh@amd.com>
To: Steve Rutherford <srutherford@google.com>, kvm@vger.kernel.org
Cc: brijesh.singh@amd.com, linux-kernel@vger.kernel.org,
natet@google.com, Ashish.Kalra@amd.com, pbonzini@redhat.com
Subject: Re: [PATCH] KVM: SVM: Add support for KVM_SEV_SEND_CANCEL command
Date: Thu, 8 Apr 2021 17:27:02 -0500 [thread overview]
Message-ID: <18c68409-5fcf-2f2c-61f2-e8e52aab277e@amd.com> (raw)
In-Reply-To: <20210402014438.1721086-1-srutherford@google.com>
On 4/1/21 8:44 PM, Steve Rutherford wrote:
> After completion of SEND_START, but before SEND_FINISH, the source VMM can
> issue the SEND_CANCEL command to stop a migration. This is necessary so
> that a cancelled migration can restart with a new target later.
>
> Signed-off-by: Steve Rutherford <srutherford@google.com>
> ---
> .../virt/kvm/amd-memory-encryption.rst | 9 +++++++
> arch/x86/kvm/svm/sev.c | 24 +++++++++++++++++++
> include/linux/psp-sev.h | 10 ++++++++
> include/uapi/linux/kvm.h | 2 ++
> 4 files changed, 45 insertions(+)
Can we add a new case statement in sev_cmd_buffer_len()
[drivers/crypto/ccp/sev-dev.c] for this command ? I understand that the
command just contains the handle. I have found dyndbg very helpful. If
the command is not added in the sev_cmd_buffer_len() then we don't dump
the command buffer.
With that fixed.
Reviewed-by: Brijesh Singh <brijesh.singh@amd.com>
next prev parent reply other threads:[~2021-04-08 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 1:44 [PATCH] KVM: SVM: Add support for KVM_SEV_SEND_CANCEL command Steve Rutherford
2021-04-08 22:02 ` Nathan Tempelman
2021-04-08 22:27 ` Brijesh Singh [this message]
2021-04-09 0:49 ` Steve Rutherford
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=18c68409-5fcf-2f2c-61f2-e8e52aab277e@amd.com \
--to=brijesh.singh@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natet@google.com \
--cc=pbonzini@redhat.com \
--cc=srutherford@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