Kashyap Chamarthy <kashyap.cv@xxxxxxxxx> wrote on 13/05/2013 10:07:02 AM: > 1/ With VMCS Shadowing *disabled* : > > - On L0 (Side note: I did reboot the host, once I disabled shadow VMCS) > ==== > $ cat /sys/module/kvm_intel/parameters/enable_shadow_vmcs > N > ==== > > - Building Kernel on L2: > ==== > $ time make > ..... > real 36m33.361s > user 18m19.003s > sys 17m6.208s > ==== > > > 2/ With VMCS Shadowing *enabled* : > > - On L0 (Side note: I did reboot the host, once I enabled shadow VMCS) > ==== > $ cat /sys/module/kvm_intel/parameters/enable_shadow_vmcs > Y > ==== > > - Building Kernel on L2: > ==== > $ time make > ..... > real 62m53.853s > user 32m32.724s > sys 32m16.430s > ==== > > Comments ? wow... according to this info shadow-vmcs is *significantly* slowing nested while it should be the opposite. Did you monitor the exit rate with and without shadow-vmcs ? -- 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
