From: Paolo Bonzini <pbonzini@redhat.com>
To: Cathy Avery <cavery@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: vkuznets@redhat.com, wei.huang2@amd.com, sean.j.christopherson@intel.com
Subject: Re: [PATCH 1/2] KVM: nSVM: Track the physical cpu of the vmcb vmrun through the vmcb
Date: Wed, 13 Jan 2021 13:09:32 +0100 [thread overview]
Message-ID: <d7b4ae9a-0011-129f-2ec4-6dd3dfe223ff@redhat.com> (raw)
In-Reply-To: <20210112164313.4204-2-cavery@redhat.com>
On 12/01/21 17:43, Cathy Avery wrote:
> void svm_switch_vmcb(struct vcpu_svm *svm, struct kvm_vmcb_info *target_vmcb)
> {
> + /*
> + * Track the old VMCB so the new VMCB will be marked
> + * dirty at its next vmrun.
> + */
> +
This comment is obsolete, otherwise looks good.
Paolo
next prev parent reply other threads:[~2021-01-13 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:43 [PATCH 0/2] KVM: SVM: Track physical cpu and asid_generation via the vmcb Cathy Avery
2021-01-12 16:43 ` [PATCH 1/2] KVM: nSVM: Track the physical cpu of the vmcb vmrun through " Cathy Avery
2021-01-13 12:09 ` Paolo Bonzini [this message]
2021-01-12 16:43 ` [PATCH 2/2] KVM: nSVM: Track the ASID generation " Cathy Avery
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=d7b4ae9a-0011-129f-2ec4-6dd3dfe223ff@redhat.com \
--to=pbonzini@redhat.com \
--cc=cavery@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wei.huang2@amd.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;
as well as URLs for NNTP newsgroup(s).