diff options
author | Sean Christopherson <sean.j.christopherson@intel.com> | 2020-07-02 19:35:34 -0700 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-07-09 13:29:40 -0400 |
commit | 5f6078f9f1e32b395a78c8d0c0f6598004c668de (patch) | |
tree | a16b5598580494a8755299dacfc60d316044fab0 /arch/x86/include/asm/kvm_host.h | |
parent | 171a90d70f25c2501162aef5f42eba5fc91c054a (diff) | |
download | linux-stable-5f6078f9f1e32b395a78c8d0c0f6598004c668de.tar.gz linux-stable-5f6078f9f1e32b395a78c8d0c0f6598004c668de.tar.bz2 linux-stable-5f6078f9f1e32b395a78c8d0c0f6598004c668de.zip |
KVM: x86/mmu: Make __GFP_ZERO a property of the memory cache
Add a gfp_zero flag to 'struct kvm_mmu_memory_cache' and use it to
control __GFP_ZERO instead of hardcoding a call to kmem_cache_zalloc().
A future patch needs such a flag for the __get_free_page() path, as
gfn arrays do not need/want the allocator to zero the memory. Convert
the kmem_cache paths to __GFP_ZERO now so as to avoid a weird and
inconsistent API in the future.
No functional change intended.
Reviewed-by: Ben Gardon <bgardon@google.com>
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Message-Id: <20200703023545.8771-11-sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/include/asm/kvm_host.h')
-rw-r--r-- | arch/x86/include/asm/kvm_host.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h index 01f5c1508851..9d41eb5a8453 100644 --- a/arch/x86/include/asm/kvm_host.h +++ b/arch/x86/include/asm/kvm_host.h @@ -251,6 +251,7 @@ struct kvm_kernel_irq_routing_entry; */ struct kvm_mmu_memory_cache { int nobjs; + gfp_t gfp_zero; struct kmem_cache *kmem_cache; void *objects[KVM_NR_MEM_OBJS]; }; |