Thanks Gleb. Here we go:
This time results appear more closer to what Ren mentioned in his
previous email - i.e. enabling VMCS Shadowing didn't "degrade", the
Kernel compile time in L2.
1] VMCS Shadowing *enabled* on L0; Kernel build on L2,
3.10.0-0.rc0.git26.1.fc20.x86_64
Kernel build time on L2
------------------------------
$ time make
[...]
real 31m0.386s
user 16m43.655s
sys 14m6.451s
kvm_stat intervals on L1
-------------------------------
-
http://kashyapc.fedorapeople.org/virt/kvm_stat-VMCS-Shadowing/kvm_stat-L0-VMCS-Shadowing-enabled.txt
- NOTE: The below statistics are from intervals ranging from
30 seconds to 6,10,13.. minutes.
2] VMCS Shadowing *disabled* on L0; Kernel build on L2,
3.10.0-0.rc0.git26.1.fc20.x86_64
Kernel build time on L2
------------------------------
$ time make
[...]
real 40m56.010s
user 20m19.061s
sys 19m57.723s
kvm_stat intervals on L1
-------------------------------
-
http://kashyapc.fedorapeople.org/virt/kvm_stat-VMCS-Shadowing/kvm_stat-L0-VMCS-Shadowing-disabled.txt
- NOTE: The below statistics are from intervals ranging from
30 seconds to 6,10,13.. minutes.
Looks better ?
(Note to self: Maybe I should run these more number of times to
monitor consistency)
Thanks,
Kashyap.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html