KVM: Explicitly use GFP_KERNEL_ACCOUNT for 'struct kvm_vcpu' allocations
Sean Christopherson
reviewerPATCH v2 1/1 KVM: Explicitly use GFP_KERNEL_ACCOUNT for 'struct kvm_vcpu' allocations
Use GFP_KERNEL_ACCOUNT when allocating vCPUs to make it more obvious that that the allocations are accounted, to make it easier to audit KVM's allocations in the future, and to be consistent with other cache usage in KVM.
When using SLAB/SLUB, this is a nop as the cache itself is created with SLAB_ACCOUNT.
When using SLOB, there are caveats within caveats. SLOB doesn't honor SLAB_ACCOUNT, so passing GFP_KERNEL_ACCOUNT will result in vCPU
allocations now being accounted. But, even that depends on internal
SLOB details as SLOB will only go to the page allocator when its cache is depleted. That just happens to be extremely likely for vCPUs because the size of kvm_vcpu is larger than the a page for almost all combinations of architecture and page size. Whether or not the SLOB behavior is by design is unknown; it's just as likely that no SLOB users care about accounding and so no one has bothered to implemented support in SLOB. Regardless, accounting vCPU allocations will not break SLOB+KVM+cgroup users, if any exist.
---
v2: Drop the Fixes tag and rewrite the changelog since this is a nop when
using SLUB or SLAB. [Wanpeng]
virt/kvm/kvm_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
virt/kvm/kvm_main.c +1 -1
@@ -3192,7 +3192,7 @@ static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, u32 id)if (r) goto vcpu_decrement; - vcpu =kmem_cache_zalloc (kvm_vcpu_cache,GFP_KERNEL ); + vcpu =kmem_cache_zalloc (kvm_vcpu_cache,GFP_KERNEL_ACCOUNT );if (!vcpu) { r = -ENOMEM ; goto vcpu_decrement;
Signature · 1 line
2.31.0.208.g409f899ff0-goog
Quoted 21 lines · Sean Christopherson
Use
GFP_KERNEL_ACCOUNTwhen allocating vCPUs to make it more obvious that that the allocations are accounted, to make it easier to audit KVM's allocations in the future, and to be consistent with other cache usage in KVM.When using SLAB/SLUB, this is a nop as the cache itself is created with
SLAB_ACCOUNT.When using SLOB, there are caveats within caveats. SLOB doesn't honor
SLAB_ACCOUNT, so passingGFP_KERNEL_ACCOUNTwill result in vCPU
allocations now being accounted. But, even that depends on internal
SLOB details as SLOB will only go to the page allocator when its cache is depleted. That just happens to be extremely likely for vCPUs because the size ofkvm_vcpuis larger than the a page for almost all combinations of architecture and page size. Whether or not the SLOB behavior is by design is unknown; it's just as likely that no SLOB users care about accounding and so no one has bothered to implemented support in SLOB. Regardless, accounting vCPU allocations will not break SLOB+KVM+cgroup users, if any exist.
Quoted 2 lines
Cc Wanpeng Li <[email protected]>Signed-off-by Sean Christopherson <[email protected]>
Quoted 24 lines
---
v2: Drop the Fixes tag and rewrite the changelog since this is a nop when
using SLUB or SLAB. [Wanpeng]virt/kvm/kvm_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)virt/kvm/kvm_main.c +1
-2@@ -3192,7 +3192,7 @@ static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, u32 id)if (r) goto vcpu_decrement; - vcpu =kmem_cache_zalloc (kvm_vcpu_cache,GFP_KERNEL ); + vcpu =kmem_cache_zalloc (kvm_vcpu_cache,GFP_KERNEL_ACCOUNT );if (!vcpu) { r = -ENOMEM ; goto vcpu_decrement; --2.31.0.208.g409f899ff0-goog
Quoted 20 lines · Sean Christopherson
Use
GFP_KERNEL_ACCOUNTwhen allocating vCPUs to make it more obvious that that the allocations are accounted, to make it easier to audit KVM's allocations in the future, and to be consistent with other cache usage in KVM.When using SLAB/SLUB, this is a nop as the cache itself is created with
SLAB_ACCOUNT.When using SLOB, there are caveats within caveats. SLOB doesn't honor
SLAB_ACCOUNT, so passingGFP_KERNEL_ACCOUNTwill result in vCPU
allocations now being accounted. But, even that depends on internal
SLOB details as SLOB will only go to the page allocator when its cache is depleted. That just happens to be extremely likely for vCPUs because the size ofkvm_vcpuis larger than the a page for almost all combinations of architecture and page size. Whether or not the SLOB behavior is by design is unknown; it's just as likely that no SLOB users care about accounding and so no one has bothered to implemented support in SLOB. Regardless, accounting vCPU allocations will not break SLOB+KVM+cgroup users, if any exist.
Quoted 2 lines
Cc Wanpeng Li <[email protected]>Signed-off-by Sean Christopherson <[email protected]>
Always happy to see this ambiguity (SLAB_ACCOUNT vs GFP_KERNEL_ACCOUNT) resolved for slab allocations.
Quoted 36 lines · Sean Christopherson
Use
GFP_KERNEL_ACCOUNTwhen allocating vCPUs to make it more obvious that that the allocations are accounted, to make it easier to audit KVM's allocations in the future, and to be consistent with other cache usage in KVM.When using SLAB/SLUB, this is a nop as the cache itself is created with
SLAB_ACCOUNT.When using SLOB, there are caveats within caveats. SLOB doesn't honor
SLAB_ACCOUNT, so passingGFP_KERNEL_ACCOUNTwill result in vCPU
allocations now being accounted. But, even that depends on internal
SLOB details as SLOB will only go to the page allocator when its cache is depleted. That just happens to be extremely likely for vCPUs because the size ofkvm_vcpuis larger than the a page for almost all combinations of architecture and page size. Whether or not the SLOB behavior is by design is unknown; it's just as likely that no SLOB users care about accounding and so no one has bothered to implemented support in SLOB. Regardless, accounting vCPU allocations will not break SLOB+KVM+cgroup users, if any exist.Cc Wanpeng Li <[email protected]>Signed-off-by Sean Christopherson <[email protected]>---
v2: Drop the Fixes tag and rewrite the changelog since this is a nop when
using SLUB or SLAB. [Wanpeng]virt/kvm/kvm_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)virt/kvm/kvm_main.c +0
-0
virt/kvm/kvm_main.c static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, u32 id) · line 3198
Quoted 8 lines
virt/kvm/kvm_main.c +1
-1@@ -3192,7 +3192,7 @@ static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, u32 id)if (r) goto vcpu_decrement; - vcpu =kmem_cache_zalloc (kvm_vcpu_cache,GFP_KERNEL ); + vcpu =kmem_cache_zalloc (kvm_vcpu_cache,GFP_KERNEL_ACCOUNT );if (!vcpu) { r = -ENOMEM ; goto vcpu_decrement;
Queued, thanks.
Paolo