Hello Paolo, On Fri, Dec 04, 2020 at 12:08:20PM +0100, Paolo Bonzini wrote: > On 05/05/20 23:18, Ashish Kalra wrote: > > Add support for static allocation of the unified Page encryption bitmap > > by extending kvm_arch_commit_memory_region() callack to add svm specific > > x86_ops which can read the userspace provided memory region/memslots and > > calculate the amount of guest RAM managed by the KVM and grow the bitmap > > based on that information, i.e. the highest guest PA that is mapped by a > > memslot. > > Hi Ashish, > > the commit message should explain why this is needed or useful. > Earlier we used to dynamic resizing of the page encryption bitmap based on the guest hypercall, but potentially a malicious guest can make a hypercall which can trigger a really large memory allocation on the host side and may eventually cause denial of service. Hence now we don't do dynamic resizing of the page encryption bitmap as per the hypercall and allocate it statically based on guest memory allocation by walking through memslots and computing it's size. I will add the above comment to the fresh series of the patch-set i am going to post. Thanks, Ashish
