From: Paolo Bonzini <pbonzini@redhat.com>
To: Ashish Kalra <Ashish.Kalra@amd.com>, seanjc@google.com
Cc: brijesh.singh@amd.com, jmattson@google.com, joro@8bytes.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
marcorr@google.com, masa.koz@kozuka.jp, pgonda@google.com,
thomas.lendacky@amd.com, vkuznets@redhat.com,
wanpengli@tencent.com
Subject: Re: [PATCH 2/2] KVM: SEV: Flush cache on non-coherent systems before RECEIVE_UPDATE_DATA
Date: Thu, 21 Oct 2021 19:01:01 +0200 [thread overview]
Message-ID: <19578a3b-e624-4002-81b0-d0346abee2f7@redhat.com> (raw)
In-Reply-To: <61709f42.1c69fb81.3b49.ecfeSMTPIN_ADDED_BROKEN@mx.google.com>
On 21/10/21 00:58, Ashish Kalra wrote:
> From: Sean Christopherson <seanjc@google.com>
>
> Hello Paolo,
>
> I am adding a SEV migration test as part of the KVM SEV selftests.
>
> And while testing SEV migration with this selftest, i observed
> cache coherency issues causing migration test failures, so really
> need this patch to be added.
>
> Tested-by: Ashish Kalra <ashish.kalra@amd.com>
>
Queued for 5.15, thanks.
Paolo
next prev parent reply other threads:[~2021-10-21 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 21:09 [PATCH 0/2] KVM: SEV: RECEIVE_UPDATE_DATA bug fixes Sean Christopherson
2021-09-14 21:09 ` [PATCH 1/2] KVM: SEV: Pin guest memory for write for RECEIVE_UPDATE_DATA Sean Christopherson
2021-09-14 22:03 ` Peter Gonda
2021-09-14 22:15 ` Brijesh Singh
2021-09-21 17:59 ` Paolo Bonzini
2021-09-14 21:09 ` [PATCH 2/2] KVM: SEV: Flush cache on non-coherent systems before RECEIVE_UPDATE_DATA Sean Christopherson
[not found] ` <61709f42.1c69fb81.3b49.ecfeSMTPIN_ADDED_BROKEN@mx.google.com>
2021-10-21 17:01 ` Paolo Bonzini [this message]
2021-10-20 22:58 ` Ashish Kalra
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=19578a3b-e624-4002-81b0-d0346abee2f7@redhat.com \
--to=pbonzini@redhat.com \
--cc=Ashish.Kalra@amd.com \
--cc=brijesh.singh@amd.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcorr@google.com \
--cc=masa.koz@kozuka.jp \
--cc=pgonda@google.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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