On Mon, Dec 3, 2018 at 1:53 PM Sean Christopherson <sean.j.christopherson@xxxxxxxxx> wrote: > > The ultimate goal of this series is to break vmx.c's monopoly on all > things VMX so that it's size goes from utterly ludicrous to merely > ridiculous. For the most part the patches are simply moving code > around. There are a few actual code changes sprinkled in, primarily > to allow moving the nested code out of vmx.c without having to expose > variables unnecessarily. Would this be a good time to think about breaking kvm's monopoly on all things vmx? That is, move the hardware VMX state management into an independent layer, so that other hypervisors could also make use of it? I'm thinking of things like global VPID allocation, tracking of which VMCS is current on each logical processor (and which VMCSs are active on each logical processor), etc.
