From: Sean Christopherson <seanjc@google.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: Wanpeng Li <wanpengli@tencent.com>,
kvm@vger.kernel.org, David Airlie <airlied@linux.ie>,
Dave Hansen <dave.hansen@linux.intel.com>,
dri-devel@lists.freedesktop.org, "H. Peter Anvin" <hpa@zytor.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
Zhi Wang <zhi.a.wang@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
intel-gfx@lists.freedesktop.org, Borislav Petkov <bp@alien8.de>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
intel-gvt-dev@lists.freedesktop.org,
Jim Mattson <jmattson@google.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [RFC PATCH v3 14/19] KVM: x86: rename .set_apic_access_page_addr to reload_apic_access_page
Date: Thu, 19 May 2022 16:55:18 +0000 [thread overview]
Message-ID: <YoZ2dh+ZujErT5nk@google.com> (raw)
In-Reply-To: <20220427200314.276673-15-mlevitsk@redhat.com>
On Wed, Apr 27, 2022, Maxim Levitsky wrote:
> This will be used on SVM to reload shadow page of the AVIC physid table
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index d2f73ce87a1e3..ad744ab99734c 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -9949,12 +9949,12 @@ void kvm_arch_mmu_notifier_invalidate_range(struct kvm *kvm,
> kvm_make_all_cpus_request(kvm, KVM_REQ_APIC_PAGE_RELOAD);
> }
>
> -static void kvm_vcpu_reload_apic_access_page(struct kvm_vcpu *vcpu)
> +static void kvm_vcpu_reload_apic_pages(struct kvm_vcpu *vcpu)
> {
> if (!lapic_in_kernel(vcpu))
> return;
>
> - static_call_cond(kvm_x86_set_apic_access_page_addr)(vcpu);
> + static_call_cond(kvm_x86_reload_apic_pages)(vcpu);
> }
>
> void __kvm_request_immediate_exit(struct kvm_vcpu *vcpu)
> @@ -10071,7 +10071,7 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
> if (kvm_check_request(KVM_REQ_LOAD_EOI_EXITMAP, vcpu))
> vcpu_load_eoi_exitmap(vcpu);
> if (kvm_check_request(KVM_REQ_APIC_PAGE_RELOAD, vcpu))
> - kvm_vcpu_reload_apic_access_page(vcpu);
> + kvm_vcpu_reload_apic_pages(vcpu);
My vote is to add a new request and new kvm_x86_ops hook instead of piggybacking
KVM_REQ_APIC_PAGE_RELOAD. The usage in kvm_arch_mmu_notifier_invalidate_range()
very subtlies relies on the memslot and vma being allocated/controlled by KVM.
The use in avic_physid_shadow_table_flush_memslot() is too similar in that it
also deals with memslot changes, but at the same time is _very_ different in that
it's dealing with user controlled memslots.
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: kvm@vger.kernel.org, Wanpeng Li <wanpengli@tencent.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ingo Molnar <mingo@redhat.com>, David Airlie <airlied@linux.ie>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, intel-gfx@lists.freedesktop.org,
Daniel Vetter <daniel@ffwll.ch>, Borislav Petkov <bp@alien8.de>,
Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, Jim Mattson <jmattson@google.com>,
Zhi Wang <zhi.a.wang@intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
"H. Peter Anvin" <hpa@zytor.com>,
intel-gvt-dev@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH v3 14/19] KVM: x86: rename .set_apic_access_page_addr to reload_apic_access_page
Date: Thu, 19 May 2022 16:55:18 +0000 [thread overview]
Message-ID: <YoZ2dh+ZujErT5nk@google.com> (raw)
In-Reply-To: <20220427200314.276673-15-mlevitsk@redhat.com>
On Wed, Apr 27, 2022, Maxim Levitsky wrote:
> This will be used on SVM to reload shadow page of the AVIC physid table
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index d2f73ce87a1e3..ad744ab99734c 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -9949,12 +9949,12 @@ void kvm_arch_mmu_notifier_invalidate_range(struct kvm *kvm,
> kvm_make_all_cpus_request(kvm, KVM_REQ_APIC_PAGE_RELOAD);
> }
>
> -static void kvm_vcpu_reload_apic_access_page(struct kvm_vcpu *vcpu)
> +static void kvm_vcpu_reload_apic_pages(struct kvm_vcpu *vcpu)
> {
> if (!lapic_in_kernel(vcpu))
> return;
>
> - static_call_cond(kvm_x86_set_apic_access_page_addr)(vcpu);
> + static_call_cond(kvm_x86_reload_apic_pages)(vcpu);
> }
>
> void __kvm_request_immediate_exit(struct kvm_vcpu *vcpu)
> @@ -10071,7 +10071,7 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
> if (kvm_check_request(KVM_REQ_LOAD_EOI_EXITMAP, vcpu))
> vcpu_load_eoi_exitmap(vcpu);
> if (kvm_check_request(KVM_REQ_APIC_PAGE_RELOAD, vcpu))
> - kvm_vcpu_reload_apic_access_page(vcpu);
> + kvm_vcpu_reload_apic_pages(vcpu);
My vote is to add a new request and new kvm_x86_ops hook instead of piggybacking
KVM_REQ_APIC_PAGE_RELOAD. The usage in kvm_arch_mmu_notifier_invalidate_range()
very subtlies relies on the memslot and vma being allocated/controlled by KVM.
The use in avic_physid_shadow_table_flush_memslot() is too similar in that it
also deals with memslot changes, but at the same time is _very_ different in that
it's dealing with user controlled memslots.
next prev parent reply other threads:[~2022-05-19 16:55 UTC|newest]
Thread overview: 159+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 20:02 [Intel-gfx] [RFC PATCH v3 00/19] RFC: nested AVIC Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-04-27 20:02 ` [Intel-gfx] [RFC PATCH v3 01/19] KVM: x86: document AVIC/APICv inhibit reasons Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-05-18 15:56 ` Sean Christopherson
2022-05-18 15:56 ` Sean Christopherson
2022-05-18 17:13 ` [Intel-gfx] " Maxim Levitsky
2022-05-18 17:13 ` Maxim Levitsky
2022-05-18 17:13 ` Maxim Levitsky
2022-04-27 20:02 ` [Intel-gfx] [RFC PATCH v3 02/19] KVM: x86: inhibit APICv/AVIC when the guest and/or host changes apic id/base from the defaults Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-05-18 8:28 ` [Intel-gfx] " Chao Gao
2022-05-18 8:28 ` Chao Gao
2022-05-18 8:28 ` Chao Gao
2022-05-18 9:50 ` [Intel-gfx] " Maxim Levitsky
2022-05-18 9:50 ` Maxim Levitsky
2022-05-18 9:50 ` Maxim Levitsky
2022-05-18 11:51 ` [Intel-gfx] " Chao Gao
2022-05-18 11:51 ` Chao Gao
2022-05-18 11:51 ` Chao Gao
2022-05-18 12:36 ` [Intel-gfx] " Maxim Levitsky
2022-05-18 12:36 ` Maxim Levitsky
2022-05-18 12:36 ` Maxim Levitsky
2022-05-18 15:39 ` Sean Christopherson
2022-05-18 15:39 ` Sean Christopherson
2022-05-18 17:15 ` [Intel-gfx] " Maxim Levitsky
2022-05-18 17:15 ` Maxim Levitsky
2022-05-18 17:15 ` Maxim Levitsky
2022-05-19 16:06 ` Sean Christopherson
2022-05-19 16:06 ` Sean Christopherson
2022-05-22 9:03 ` [Intel-gfx] " Maxim Levitsky
2022-05-22 9:03 ` Maxim Levitsky
2022-05-22 9:03 ` Maxim Levitsky
2022-05-22 14:47 ` Jim Mattson
2022-05-22 14:47 ` Jim Mattson
2022-05-23 6:50 ` [Intel-gfx] " Maxim Levitsky
2022-05-23 6:50 ` Maxim Levitsky
2022-05-23 6:50 ` Maxim Levitsky
2022-05-23 17:22 ` Jim Mattson
2022-05-23 17:22 ` Jim Mattson
2022-05-23 17:31 ` Sean Christopherson
2022-05-23 17:31 ` Sean Christopherson
2022-06-23 9:44 ` [Intel-gfx] " Maxim Levitsky
2022-06-23 9:44 ` Maxim Levitsky
2022-06-23 9:44 ` Maxim Levitsky
2022-04-27 20:02 ` [Intel-gfx] [RFC PATCH v3 03/19] KVM: x86: SVM: remove avic's broken code that updated APIC ID Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-05-19 16:10 ` Sean Christopherson
2022-05-19 16:10 ` Sean Christopherson
2022-05-22 9:01 ` [Intel-gfx] " Maxim Levitsky
2022-05-22 9:01 ` Maxim Levitsky
2022-05-22 9:01 ` Maxim Levitsky
2022-05-23 17:19 ` Sean Christopherson
2022-05-23 17:19 ` Sean Christopherson
2022-04-27 20:02 ` [Intel-gfx] [RFC PATCH v3 04/19] KVM: x86: mmu: allow to enable write tracking externally Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-04-27 20:02 ` Maxim Levitsky
2022-05-19 16:27 ` Sean Christopherson
2022-05-19 16:27 ` Sean Christopherson
2022-05-22 10:21 ` [Intel-gfx] " Maxim Levitsky
2022-05-22 10:21 ` Maxim Levitsky
2022-05-22 10:21 ` Maxim Levitsky
2022-05-19 16:37 ` Sean Christopherson
2022-05-19 16:37 ` Sean Christopherson
2022-05-22 10:22 ` [Intel-gfx] " Maxim Levitsky
2022-05-22 10:22 ` Maxim Levitsky
2022-05-22 10:22 ` Maxim Levitsky
2022-07-20 14:42 ` [Intel-gfx] " Maxim Levitsky
2022-07-20 14:42 ` Maxim Levitsky
2022-07-20 14:42 ` Maxim Levitsky
2022-07-25 16:08 ` [Intel-gfx] " Sean Christopherson
2022-07-25 16:08 ` Sean Christopherson
2022-07-25 16:08 ` Sean Christopherson
2022-07-28 7:46 ` [Intel-gfx] " Maxim Levitsky
2022-07-28 7:46 ` Maxim Levitsky
2022-07-28 7:46 ` Maxim Levitsky
2022-08-01 15:53 ` [Intel-gfx] " Maxim Levitsky
2022-08-01 15:53 ` Maxim Levitsky
2022-08-01 15:53 ` Maxim Levitsky
2022-08-01 17:20 ` [Intel-gfx] " Sean Christopherson
2022-08-01 17:20 ` Sean Christopherson
2022-08-01 17:20 ` Sean Christopherson
2022-08-08 13:13 ` [Intel-gfx] Nested AVIC design (was:Re: [RFC PATCH v3 04/19] KVM: x86: mmu: allow to enable write tracking externally) Maxim Levitsky
2022-08-08 13:13 ` Maxim Levitsky
2022-08-08 13:13 ` Maxim Levitsky
2022-09-29 22:38 ` [Intel-gfx] " Sean Christopherson
2022-09-29 22:38 ` Sean Christopherson
2022-09-29 22:38 ` Sean Christopherson
2022-10-03 7:27 ` [Intel-gfx] " Maxim Levitsky
2022-10-03 7:27 ` Maxim Levitsky
2022-10-03 7:27 ` Maxim Levitsky
2022-11-10 0:47 ` [Intel-gfx] " Sean Christopherson
2022-11-10 0:47 ` Sean Christopherson
2022-11-10 0:47 ` Sean Christopherson
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 05/19] x86: KVMGT: use kvm_page_track_write_tracking_enable Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-05-19 16:38 ` Sean Christopherson
2022-05-19 16:38 ` Sean Christopherson
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 06/19] KVM: x86: mmu: add gfn_in_memslot helper Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-05-19 16:43 ` Sean Christopherson
2022-05-19 16:43 ` Sean Christopherson
2022-05-22 10:22 ` [Intel-gfx] " Maxim Levitsky
2022-05-22 10:22 ` Maxim Levitsky
2022-05-22 10:22 ` Maxim Levitsky
2022-05-22 12:12 ` [Intel-gfx] " Maxim Levitsky
2022-05-22 12:12 ` Maxim Levitsky
2022-05-22 12:12 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 07/19] KVM: x86: mmu: tweak fast path for emulation of access to nested NPT pages Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 08/19] KVM: x86: SVM: move avic state to separate struct Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 09/19] KVM: x86: nSVM: add nested AVIC tracepoints Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 10/19] KVM: x86: nSVM: implement AVIC's physid/logid table access helpers Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 11/19] KVM: x86: nSVM: implement shadowing of AVIC's physical id table Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 12/19] KVM: x86: nSVM: make nested AVIC physid write tracking be aware of the host scheduling Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 13/19] KVM: x86: nSVM: wire nested AVIC to nested guest entry/exit Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 14/19] KVM: x86: rename .set_apic_access_page_addr to reload_apic_access_page Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-05-19 16:55 ` Sean Christopherson [this message]
2022-05-19 16:55 ` Sean Christopherson
2022-05-22 10:22 ` [Intel-gfx] " Maxim Levitsky
2022-05-22 10:22 ` Maxim Levitsky
2022-05-22 10:22 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 15/19] KVM: x86: nSVM: add code to reload AVIC physid table when it is invalidated Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 16/19] KVM: x86: nSVM: implement support for nested AVIC vmexits Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 17/19] KVM: x86: nSVM: implement nested AVIC doorbell emulation Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 18/19] KVM: x86: SVM/nSVM: add optional non strict AVIC doorbell mode Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` [Intel-gfx] [RFC PATCH v3 19/19] KVM: x86: nSVM: expose the nested AVIC to the guest Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:03 ` Maxim Levitsky
2022-04-27 20:11 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for RFC: nested AVIC (rev2) Patchwork
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=YoZ2dh+ZujErT5nk@google.com \
--to=seanjc@google.com \
--cc=airlied@linux.ie \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--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=pbonzini@redhat.com \
--cc=rodrigo.vivi@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=zhi.a.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.