On 12/04/2018 18:53, Jim Mattson wrote: >> cpuid info could definitely be moved to a separate vmalloc-ed block, as >> a start. >> >> Paolo > It's a small start, but it won't get us down to order 3... > > (gdb) p sizeof(((struct kvm_vcpu_arch *)0)->cpuid_entries) > $1 = 3200 > > What is the objection to a single vmalloc for the entire structure? Is > there anything in there that needs physically contiguous pages? No objection, just that I didn't know offhand. If it works, let's go for it. Paolo
