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 04/19] KVM: x86: mmu: allow to enable write tracking externally
Date: Thu, 19 May 2022 16:27:28 +0000 [thread overview]
Message-ID: <YoZv8HmRc7tqQbuL@google.com> (raw)
In-Reply-To: <20220427200314.276673-5-mlevitsk@redhat.com>
On Wed, Apr 27, 2022, Maxim Levitsky wrote:
> This will be used to enable write tracking from nested AVIC code
> and can also be used to enable write tracking in GVT-g module
> when it actually uses it as opposed to always enabling it,
> when the module is compiled in the kernel.
Wrap at ~75.
> No functional change intended.
>
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> ---
> arch/x86/include/asm/kvm_host.h | 2 +-
> arch/x86/include/asm/kvm_page_track.h | 1 +
> arch/x86/kvm/mmu.h | 8 +++++---
> arch/x86/kvm/mmu/mmu.c | 17 ++++++++++-------
> arch/x86/kvm/mmu/page_track.c | 10 ++++++++--
> 5 files changed, 25 insertions(+), 13 deletions(-)
>
> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
> index 636df87542555..fc7df778a3d71 100644
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -1254,7 +1254,7 @@ struct kvm_arch {
> * is used as one input when determining whether certain memslot
> * related allocations are necessary.
> */
The above comment needs to be rewritten.
> - bool shadow_root_allocated;
> + bool mmu_page_tracking_enabled;
> #if IS_ENABLED(CONFIG_HYPERV)
> hpa_t hv_root_tdp;
> diff --git a/arch/x86/include/asm/kvm_page_track.h b/arch/x86/include/asm/kvm_page_track.h
> index eb186bc57f6a9..955a5ae07b10e 100644
> --- a/arch/x86/include/asm/kvm_page_track.h
> +++ b/arch/x86/include/asm/kvm_page_track.h
> @@ -50,6 +50,7 @@ int kvm_page_track_init(struct kvm *kvm);
> void kvm_page_track_cleanup(struct kvm *kvm);
>
> bool kvm_page_track_write_tracking_enabled(struct kvm *kvm);
> +int kvm_page_track_write_tracking_enable(struct kvm *kvm);
> int kvm_page_track_write_tracking_alloc(struct kvm_memory_slot *slot);
>
> void kvm_page_track_free_memslot(struct kvm_memory_slot *slot);
> diff --git a/arch/x86/kvm/mmu.h b/arch/x86/kvm/mmu.h
> index 671cfeccf04e9..44d15551f7156 100644
> --- a/arch/x86/kvm/mmu.h
> +++ b/arch/x86/kvm/mmu.h
> @@ -269,7 +269,7 @@ int kvm_arch_write_log_dirty(struct kvm_vcpu *vcpu);
> int kvm_mmu_post_init_vm(struct kvm *kvm);
> void kvm_mmu_pre_destroy_vm(struct kvm *kvm);
>
> -static inline bool kvm_shadow_root_allocated(struct kvm *kvm)
> +static inline bool mmu_page_tracking_enabled(struct kvm *kvm)
> {
> /*
> * Read shadow_root_allocated before related pointers. Hence, threads
> @@ -277,9 +277,11 @@ static inline bool kvm_shadow_root_allocated(struct kvm *kvm)
> * see the pointers. Pairs with smp_store_release in
> * mmu_first_shadow_root_alloc.
> */
This comment also needs to be rewritten.
> - return smp_load_acquire(&kvm->arch.shadow_root_allocated);
> + return smp_load_acquire(&kvm->arch.mmu_page_tracking_enabled);
> }
...
> diff --git a/arch/x86/kvm/mmu/page_track.c b/arch/x86/kvm/mmu/page_track.c
> index 2e09d1b6249f3..8857d629036d7 100644
> --- a/arch/x86/kvm/mmu/page_track.c
> +++ b/arch/x86/kvm/mmu/page_track.c
> @@ -21,10 +21,16 @@
>
> bool kvm_page_track_write_tracking_enabled(struct kvm *kvm)
This can be static, it's now used only by page_track.c.
> {
> - return IS_ENABLED(CONFIG_KVM_EXTERNAL_WRITE_TRACKING) ||
> - !tdp_enabled || kvm_shadow_root_allocated(kvm);
> + return mmu_page_tracking_enabled(kvm);
> }
>
> +int kvm_page_track_write_tracking_enable(struct kvm *kvm)
This is too similar to the "enabled" version; "kvm_page_track_enable_write_tracking()"
would maintain namespacing and be less confusing.
Hmm, I'd probably vote to make this a "static inline" in kvm_page_track.h, and
rename mmu_enable_write_tracking() to kvm_mmu_enable_write_tracking and export.
Not a strong preference, just feels silly to export a one-liner.
> +{
> + return mmu_enable_write_tracking(kvm);
> +}
> +EXPORT_SYMBOL_GPL(kvm_page_track_write_tracking_enable);
> +
> +
> void kvm_page_track_free_memslot(struct kvm_memory_slot *slot)
> {
> int i;
> --
> 2.26.3
>
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 04/19] KVM: x86: mmu: allow to enable write tracking externally
Date: Thu, 19 May 2022 16:27:28 +0000 [thread overview]
Message-ID: <YoZv8HmRc7tqQbuL@google.com> (raw)
In-Reply-To: <20220427200314.276673-5-mlevitsk@redhat.com>
On Wed, Apr 27, 2022, Maxim Levitsky wrote:
> This will be used to enable write tracking from nested AVIC code
> and can also be used to enable write tracking in GVT-g module
> when it actually uses it as opposed to always enabling it,
> when the module is compiled in the kernel.
Wrap at ~75.
> No functional change intended.
>
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> ---
> arch/x86/include/asm/kvm_host.h | 2 +-
> arch/x86/include/asm/kvm_page_track.h | 1 +
> arch/x86/kvm/mmu.h | 8 +++++---
> arch/x86/kvm/mmu/mmu.c | 17 ++++++++++-------
> arch/x86/kvm/mmu/page_track.c | 10 ++++++++--
> 5 files changed, 25 insertions(+), 13 deletions(-)
>
> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
> index 636df87542555..fc7df778a3d71 100644
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -1254,7 +1254,7 @@ struct kvm_arch {
> * is used as one input when determining whether certain memslot
> * related allocations are necessary.
> */
The above comment needs to be rewritten.
> - bool shadow_root_allocated;
> + bool mmu_page_tracking_enabled;
> #if IS_ENABLED(CONFIG_HYPERV)
> hpa_t hv_root_tdp;
> diff --git a/arch/x86/include/asm/kvm_page_track.h b/arch/x86/include/asm/kvm_page_track.h
> index eb186bc57f6a9..955a5ae07b10e 100644
> --- a/arch/x86/include/asm/kvm_page_track.h
> +++ b/arch/x86/include/asm/kvm_page_track.h
> @@ -50,6 +50,7 @@ int kvm_page_track_init(struct kvm *kvm);
> void kvm_page_track_cleanup(struct kvm *kvm);
>
> bool kvm_page_track_write_tracking_enabled(struct kvm *kvm);
> +int kvm_page_track_write_tracking_enable(struct kvm *kvm);
> int kvm_page_track_write_tracking_alloc(struct kvm_memory_slot *slot);
>
> void kvm_page_track_free_memslot(struct kvm_memory_slot *slot);
> diff --git a/arch/x86/kvm/mmu.h b/arch/x86/kvm/mmu.h
> index 671cfeccf04e9..44d15551f7156 100644
> --- a/arch/x86/kvm/mmu.h
> +++ b/arch/x86/kvm/mmu.h
> @@ -269,7 +269,7 @@ int kvm_arch_write_log_dirty(struct kvm_vcpu *vcpu);
> int kvm_mmu_post_init_vm(struct kvm *kvm);
> void kvm_mmu_pre_destroy_vm(struct kvm *kvm);
>
> -static inline bool kvm_shadow_root_allocated(struct kvm *kvm)
> +static inline bool mmu_page_tracking_enabled(struct kvm *kvm)
> {
> /*
> * Read shadow_root_allocated before related pointers. Hence, threads
> @@ -277,9 +277,11 @@ static inline bool kvm_shadow_root_allocated(struct kvm *kvm)
> * see the pointers. Pairs with smp_store_release in
> * mmu_first_shadow_root_alloc.
> */
This comment also needs to be rewritten.
> - return smp_load_acquire(&kvm->arch.shadow_root_allocated);
> + return smp_load_acquire(&kvm->arch.mmu_page_tracking_enabled);
> }
...
> diff --git a/arch/x86/kvm/mmu/page_track.c b/arch/x86/kvm/mmu/page_track.c
> index 2e09d1b6249f3..8857d629036d7 100644
> --- a/arch/x86/kvm/mmu/page_track.c
> +++ b/arch/x86/kvm/mmu/page_track.c
> @@ -21,10 +21,16 @@
>
> bool kvm_page_track_write_tracking_enabled(struct kvm *kvm)
This can be static, it's now used only by page_track.c.
> {
> - return IS_ENABLED(CONFIG_KVM_EXTERNAL_WRITE_TRACKING) ||
> - !tdp_enabled || kvm_shadow_root_allocated(kvm);
> + return mmu_page_tracking_enabled(kvm);
> }
>
> +int kvm_page_track_write_tracking_enable(struct kvm *kvm)
This is too similar to the "enabled" version; "kvm_page_track_enable_write_tracking()"
would maintain namespacing and be less confusing.
Hmm, I'd probably vote to make this a "static inline" in kvm_page_track.h, and
rename mmu_enable_write_tracking() to kvm_mmu_enable_write_tracking and export.
Not a strong preference, just feels silly to export a one-liner.
> +{
> + return mmu_enable_write_tracking(kvm);
> +}
> +EXPORT_SYMBOL_GPL(kvm_page_track_write_tracking_enable);
> +
> +
> void kvm_page_track_free_memslot(struct kvm_memory_slot *slot)
> {
> int i;
> --
> 2.26.3
>
next prev parent reply other threads:[~2022-05-19 16:27 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 [this message]
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
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=YoZv8HmRc7tqQbuL@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.