On 07/14/2011 04:12 PM, Joerg Roedel wrote:
Makes sense. I'll probably remove the lazy allocation and initialize
both VMCBs at vcpu-creation time. The memory foodprint is the same as
before because the hsave area was also allocated at the beginning.
Related, would we need a pool of n_vmcbs/vmcb02s?
I guess the condition for reusing an n_vmcb would be: same vmcb_gpa and
at least one clean bit set?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
