[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3737d3b5-0569-bba3-cda1-9967e9651365@redhat.com>
Date: Fri, 31 Jul 2020 00:49:24 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Babu Moger <babu.moger@....com>, Jim Mattson <jmattson@...gle.com>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
kvm list <kvm@...r.kernel.org>, Joerg Roedel <joro@...tes.org>,
the arch/x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v3 03/11] KVM: SVM: Change intercept_dr to generic
intercepts
On 31/07/20 00:41, Babu Moger wrote:
>> Let me try to understand.
>>
>> vmcb01 is &svm->vmcb->control;l
>> vmcb02 is &svm->nested.hsave->control
>> vmcb12 is &svm->nested.ctl;
Right now we don't have a separate vmcb01/vmcb02, we have the current
and hsave VMCBs. Cathy is working on it.
Just do the refactoring by passing the control area to
vmcb_set_intercept/vmcb_clr_intercept/vmcb_is_intercept.
>> The functions set_intercept and clr_intercept calls get_host_vmcb to get the
>> vmcb address.
>
> I will move the get_host_vmcb inside the caller and then call
> vmcb_set_intercept/vmcb_clr_intercept/vmcb_is_intercept directly.
Hmm no I think set_intercept and clr_intercept should remain as is.
Paolo
> I will re post the series. This will change the whole series a little bit.
Powered by blists - more mailing lists