• W
    KVM: X86: Dynamically allocate user_fpu · d9a710e5
    Wanpeng Li 提交于
    After reverting commit 240c35a3 (kvm: x86: Use task structs fpu field
    for user), struct kvm_vcpu is 19456 bytes on my server, PAGE_ALLOC_COSTLY_ORDER(3)
    is the order at which allocations are deemed costly to service. In serveless
    scenario, one host can service hundreds/thoudands firecracker/kata-container
    instances, howerver, new instance will fail to launch after memory is too
    fragmented to allocate kvm_vcpu struct on host, this was observed in some
    cloud provider product environments.
    
    This patch dynamically allocates user_fpu, kvm_vcpu is 15168 bytes now on my
    Skylake server.
    
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Radim Krčmář <rkrcmar@redhat.com>
    Signed-off-by: NWanpeng Li <wanpengli@tencent.com>
    Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
    d9a710e5
x86.c 258.9 KB