From: Vitaly Kuznetsov <vkuznets@redhat.com> To: "Suthikulpanit\, Suravee" <Suravee.Suthikulpanit@amd.com> Cc: "pbonzini\@redhat.com" <pbonzini@redhat.com>, "rkrcmar\@redhat.com" <rkrcmar@redhat.com>, "joro\@8bytes.org" <joro@8bytes.org>, "graf\@amazon.com" <graf@amazon.com>, "jschoenh\@amazon.de" <jschoenh@amazon.de>, "karahmed\@amazon.de" <karahmed@amazon.de>, "rimasluk\@amazon.com" <rimasluk@amazon.com>, "Grimm\, Jon" <Jon.Grimm@amd.com>, "Suthikulpanit\, Suravee" <Suravee.Suthikulpanit@amd.com>, "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>, "kvm\@vger.kernel.org" <kvm@vger.kernel.org> Subject: Re: [PATCH v2 01/15] kvm: x86: Modify kvm_x86_ops.get_enable_apicv() to use struct kvm parameter Date: Tue, 27 Aug 2019 09:15:18 +0200 Message-ID: <87d0grm649.fsf@vitty.brq.redhat.com> (raw) In-Reply-To: <1565886293-115836-2-git-send-email-suravee.suthikulpanit@amd.com> "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com> writes: > Generally, APICv for all vcpus in the VM are enable/disable in the same > manner. So, get_enable_apicv() should represent APICv status of the VM > instead of each VCPU. > > Modify kvm_x86_ops.get_enable_apicv() to take struct kvm as parameter > instead of struct kvm_vcpu. > > Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> > --- > arch/x86/include/asm/kvm_host.h | 2 +- > arch/x86/kvm/svm.c | 5 +++-- > arch/x86/kvm/vmx/vmx.c | 2 +- > arch/x86/kvm/x86.c | 2 +- > 4 files changed, 6 insertions(+), 5 deletions(-) > > diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h > index 26d1eb8..56bc702 100644 > --- a/arch/x86/include/asm/kvm_host.h > +++ b/arch/x86/include/asm/kvm_host.h > @@ -1077,7 +1077,7 @@ struct kvm_x86_ops { > void (*enable_nmi_window)(struct kvm_vcpu *vcpu); > void (*enable_irq_window)(struct kvm_vcpu *vcpu); > void (*update_cr8_intercept)(struct kvm_vcpu *vcpu, int tpr, int irr); > - bool (*get_enable_apicv)(struct kvm_vcpu *vcpu); > + bool (*get_enable_apicv)(struct kvm *kvm); > void (*refresh_apicv_exec_ctrl)(struct kvm_vcpu *vcpu); > void (*hwapic_irr_update)(struct kvm_vcpu *vcpu, int max_irr); > void (*hwapic_isr_update)(struct kvm_vcpu *vcpu, int isr); > diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c > index ccd5aa6..6851bce 100644 > --- a/arch/x86/kvm/svm.c > +++ b/arch/x86/kvm/svm.c > @@ -384,6 +384,7 @@ struct amd_svm_iommu_ir { > static void svm_set_cr0(struct kvm_vcpu *vcpu, unsigned long cr0); > static void svm_flush_tlb(struct kvm_vcpu *vcpu, bool invalidate_gpa); > static void svm_complete_interrupts(struct vcpu_svm *svm); > +static bool svm_get_enable_apicv(struct kvm *kvm); Why is this forward declaration needed [in this patch]? > > static int nested_svm_exit_handled(struct vcpu_svm *svm); > static int nested_svm_intercept(struct vcpu_svm *svm); > @@ -5124,9 +5125,9 @@ static void svm_set_virtual_apic_mode(struct kvm_vcpu *vcpu) > return; > } > > -static bool svm_get_enable_apicv(struct kvm_vcpu *vcpu) > +static bool svm_get_enable_apicv(struct kvm *kvm) > { > - return avic && irqchip_split(vcpu->kvm); > + return avic && irqchip_split(kvm); > } > > static void svm_hwapic_irr_update(struct kvm_vcpu *vcpu, int max_irr) > diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c > index d98eac3..18a4b94 100644 > --- a/arch/x86/kvm/vmx/vmx.c > +++ b/arch/x86/kvm/vmx/vmx.c > @@ -3610,7 +3610,7 @@ void pt_update_intercept_for_msr(struct vcpu_vmx *vmx) > } > } > > -static bool vmx_get_enable_apicv(struct kvm_vcpu *vcpu) > +static bool vmx_get_enable_apicv(struct kvm *kvm) > { > return enable_apicv; > } > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index fafd81d..7daf0dd 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -9150,7 +9150,7 @@ int kvm_arch_vcpu_init(struct kvm_vcpu *vcpu) > goto fail_free_pio_data; > > if (irqchip_in_kernel(vcpu->kvm)) { > - vcpu->arch.apicv_active = kvm_x86_ops->get_enable_apicv(vcpu); > + vcpu->arch.apicv_active = kvm_x86_ops->get_enable_apicv(vcpu->kvm); > r = kvm_create_lapic(vcpu, lapic_timer_advance_ns); > if (r < 0) > goto fail_mmu_destroy; With the above question answered (or declaration moved to the patch where it's actually needed) Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com> -- Vitaly
next prev parent reply index Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-15 16:25 [PATCH v2 00/15] kvm: x86: Support AMD SVM AVIC w/ in-kernel irqchip mode Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 01/15] kvm: x86: Modify kvm_x86_ops.get_enable_apicv() to use struct kvm parameter Suthikulpanit, Suravee 2019-08-27 7:15 ` Vitaly Kuznetsov [this message] 2019-08-15 16:25 ` [PATCH v2 02/15] kvm: x86: Introduce KVM APICv state Suthikulpanit, Suravee 2019-08-19 9:49 ` Alexander Graf 2019-08-26 19:06 ` Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 03/15] kvm: Add arch-specific per-VM debugfs support Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 04/15] kvm: x86: Add per-VM APICv state debugfs Suthikulpanit, Suravee 2019-08-19 9:57 ` Alexander Graf 2019-08-26 19:41 ` Suthikulpanit, Suravee 2019-08-27 8:20 ` Alexander Graf 2019-08-28 18:39 ` Suthikulpanit, Suravee 2019-08-28 19:36 ` Graf (AWS), Alexander 2019-08-15 16:25 ` [PATCH v2 05/15] kvm: lapic: Introduce APICv update helper function Suthikulpanit, Suravee 2019-08-27 7:22 ` Vitaly Kuznetsov 2019-08-15 16:25 ` [PATCH v2 06/15] kvm: x86: Add support for activate/de-activate APICv at runtime Suthikulpanit, Suravee 2019-08-27 7:29 ` Vitaly Kuznetsov 2019-08-27 8:05 ` Alexander Graf 2019-08-15 16:25 ` [PATCH v2 07/15] kvm: x86: svm: Add support to activate/deactivate posted interrupts Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 08/15] svm: Add support for setup/destroy virutal APIC backing page for AVIC Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 09/15] svm: Add support for activate/deactivate AVIC at runtime Suthikulpanit, Suravee 2019-08-19 10:28 ` Alexander Graf 2019-08-15 16:25 ` [PATCH v2 10/15] kvm: x86: hyperv: Use APICv deactivate request interface Suthikulpanit, Suravee 2019-08-19 10:31 ` Alexander Graf 2019-08-15 16:25 ` [PATCH v2 11/15] svm: Temporary deactivate AVIC during ExtINT handling Suthikulpanit, Suravee 2019-08-19 10:35 ` Alexander Graf 2019-08-28 15:17 ` Suthikulpanit, Suravee 2019-08-28 19:37 ` Graf (AWS), Alexander 2019-09-10 15:46 ` Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 12/15] kvm: i8254: Check LAPIC EOI pending when injecting irq on SVM AVIC Suthikulpanit, Suravee 2019-08-19 10:42 ` Alexander Graf 2019-08-26 20:46 ` Suthikulpanit, Suravee 2019-08-27 9:10 ` Alexander Graf 2019-09-13 14:50 ` Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 13/15] kvm: lapic: Clean up APIC predefined macros Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 14/15] kvm: ioapic: Delay update IOAPIC EOI for RTC Suthikulpanit, Suravee 2019-08-19 11:00 ` Alexander Graf 2019-09-04 2:06 ` Suthikulpanit, Suravee 2019-08-15 16:25 ` [PATCH v2 15/15] svm: Allow AVIC with in-kernel irqchip mode Suthikulpanit, Suravee
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=87d0grm649.fsf@vitty.brq.redhat.com \ --to=vkuznets@redhat.com \ --cc=Jon.Grimm@amd.com \ --cc=Suravee.Suthikulpanit@amd.com \ --cc=graf@amazon.com \ --cc=joro@8bytes.org \ --cc=jschoenh@amazon.de \ --cc=karahmed@amazon.de \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=pbonzini@redhat.com \ --cc=rimasluk@amazon.com \ --cc=rkrcmar@redhat.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
KVM Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/kvm/0 kvm/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 kvm kvm/ https://lore.kernel.org/kvm \ kvm@vger.kernel.org public-inbox-index kvm Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.kvm AGPL code for this site: git clone https://public-inbox.org/public-inbox.git