From: "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Cc: "joro@8bytes.org" <joro@8bytes.org>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [PATCH] svm: Fix improper check when deactivate AVIC
Date: Mon, 4 Feb 2019 16:05:59 +0000 [thread overview]
Message-ID: <a845d403-be02-ef43-2673-01b265e77fb3@amd.com> (raw)
In-Reply-To: <e587eb0a-cd73-bbf9-5a77-1cc598bd49ac@amd.com>
Paolo,
On 2/1/19 6:01 PM, Suravee Suthikulpanit wrote:
> Paolo,
>
> On 1/30/19 11:22 PM, Paolo Bonzini wrote:
>> On 29/01/19 09:09, Suthikulpanit, Suravee wrote:
>>> The function svm_refresh_apicv_exec_ctrl() always returning prematurely
>>> as kvm_vcpu_apicv_active() always return false when calling from
>>> the function arch/x86/kvm/x86.c:kvm_vcpu_deactivate_apicv().
>>> This is because the apicv_active is set to false just before calling
>>> refresh_apicv_exec_ctrl().
>>>
>>> Also, we need to mark VMCB_AVIC bit as dirty instead of VMCB_INTR.
>>>
>>> So, fix svm_refresh_apicv_exec_ctrl() to properly deactivate AVIC.
>>>
>>> Fixes: 67034bb9dd5e ('KVM: SVM: Add irqchip_split() checks before enabling AVIC')
>>
>> Having the lapic_in_kernel check in your code is a bit ugly - the caller
>> should check it. And actually, even though it doesn't check it right
>> now, svm_refresh_apicv_exec_ctrl is only reachable if lapic_in_kernel
>> returns true; see the KVM_CAP_HYPERV_SYNIC case of
>> kvm_vcpu_ioctl_enable_cap.
>>
>> What about this simpler patch:
>>
>> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
>> index 01b66bbcdd7a..74ceda470eae 100644
>> --- a/arch/x86/kvm/svm.c
>> +++ b/arch/x86/kvm/svm.c
>> @@ -5122,11 +5122,11 @@ static void svm_refresh_apicv_exec_ctrl(
>> struct vcpu_svm *svm = to_svm(vcpu);
>> struct vmcb *vmcb = svm->vmcb;
>>
>> - if (!kvm_vcpu_apicv_active(&svm->vcpu))
>> - return;
>> -
>> - vmcb->control.int_ctl &= ~AVIC_ENABLE_MASK;
>> - mark_dirty(vmcb, VMCB_INTR);
>> + if (kvm_vcpu_apicv_active(vcpu))
>> + vmcb->control.int_ctl |= AVIC_ENABLE_MASK;
>> + else
>> + vmcb->control.int_ctl &= ~AVIC_ENABLE_MASK;
>> + mark_dirty(vmcb, VMCB_AVIC);
>> }
>>
>> static void svm_load_eoi_exitmap(struct kvm_vcpu *vcpu, u64
>> *eoi_exit_bitmap)
>>
>> ?
>>
>> Thanks,
>>
>> Paolo
>>
>
> Yes, this would work.
>
> This patch is actually a precursor of a patch series that I am working on
> to allow AVIC enabling/disabling during run-time. I will send out a series
> for RFC soon.
>
> Thanks,
> Suravee
Not sure if you have already applied this change. Anyhow, I just want to let
you know that I have included the change you suggested as patch 1/8 of
the RFC series
"KVM: x86: svm: Enabling AVIC with in kernel irqchip"
Thanks,
Suravee
prev parent reply other threads:[~2019-02-04 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 8:09 Suthikulpanit, Suravee
2019-01-30 16:22 ` Paolo Bonzini
2019-02-01 11:01 ` Suthikulpanit, Suravee
2019-02-04 16:05 ` Suthikulpanit, Suravee [this message]
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=a845d403-be02-ef43-2673-01b265e77fb3@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®