From: Paolo Bonzini <pbonzini@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, kvm@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Sean Christopherson <seanjc@google.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jim Mattson <jmattson@google.com>,
x86@kernel.org, Vitaly Kuznetsov <vkuznets@redhat.com>,
Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, Wanpeng Li <wanpengli@tencent.com>
Subject: Re: [PATCH v3 1/7] KVM: x86: nSVM: correctly virtualize LBR msrs when L2 is running
Date: Wed, 9 Mar 2022 14:00:04 +0100 [thread overview]
Message-ID: <e38f0d14-419d-7b3d-4ce4-bd37200ba232@redhat.com> (raw)
In-Reply-To: <20220301143650.143749-2-mlevitsk@redhat.com>
On 3/1/22 15:36, Maxim Levitsky wrote:
> +void svm_copy_lbrs(struct vmcb *from_vmcb, struct vmcb *to_vmcb)
> +{
> + to_vmcb->save.dbgctl = from_vmcb->save.dbgctl;
> + to_vmcb->save.br_from = from_vmcb->save.br_from;
> + to_vmcb->save.br_to = from_vmcb->save.br_to;
> + to_vmcb->save.last_excp_from = from_vmcb->save.last_excp_from;
> + to_vmcb->save.last_excp_to = from_vmcb->save.last_excp_to;
> +
> + vmcb_mark_dirty(to_vmcb, VMCB_LBR);
> +}
> +
I think "struct vmcb *to_vmcb, struct vmcb *from_vmcb" is more common
(e.g. svm_copy_vmrun_state, svm_copy_vmloadsave_state).
Paolo
next prev parent reply other threads:[~2022-03-09 13:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 14:36 [PATCH v3 0/7] nSVM/SVM features Maxim Levitsky
2022-03-01 14:36 ` [PATCH v3 1/7] KVM: x86: nSVM: correctly virtualize LBR msrs when L2 is running Maxim Levitsky
2022-03-09 13:00 ` Paolo Bonzini [this message]
2022-03-14 11:25 ` Maxim Levitsky
2022-03-01 14:36 ` [PATCH v3 2/7] KVM: x86: nSVM: implement nested LBR virtualization Maxim Levitsky
2022-03-09 13:00 ` Paolo Bonzini
2022-03-22 16:53 ` Maxim Levitsky
2022-03-01 14:36 ` [PATCH v3 3/7] KVM: x86: nSVM: implement nested VMLOAD/VMSAVE Maxim Levitsky
2022-03-01 14:36 ` [PATCH v3 4/7] KVM: x86: nSVM: support PAUSE filter threshold and count when cpu_pm=on Maxim Levitsky
2022-03-09 13:12 ` Paolo Bonzini
2022-03-22 16:52 ` Maxim Levitsky
2022-03-09 18:35 ` Jim Mattson
2022-03-09 18:47 ` Paolo Bonzini
2022-03-09 19:07 ` Jim Mattson
2022-03-21 21:36 ` Maxim Levitsky
2022-03-21 21:59 ` Jim Mattson
2022-03-21 22:11 ` Maxim Levitsky
2022-03-21 22:41 ` Jim Mattson
2022-03-22 10:12 ` Paolo Bonzini
2022-03-22 11:17 ` Maxim Levitsky
2022-03-01 14:36 ` [PATCH v3 5/7] KVM: x86: nSVM: implement nested vGIF Maxim Levitsky
2022-03-09 13:40 ` Paolo Bonzini
2022-03-14 15:21 ` Maxim Levitsky
2022-03-01 14:36 ` [PATCH v3 6/7] KVM: x86: SVM: allow to force AVIC to be enabled Maxim Levitsky
2022-03-09 13:41 ` Paolo Bonzini
2022-03-01 14:36 ` [PATCH v3 7/7] KVM: x86: SVM: allow AVIC to co-exist with a nested guest running Maxim Levitsky
2022-03-09 13:50 ` Paolo Bonzini
2022-03-09 18:14 ` Maxim Levitsky
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=e38f0d14-419d-7b3d-4ce4-bd37200ba232@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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).