Avi Kivity wrote:d led IMHO, I think it is better to let kvm_guest_exit() empty (you can remove = it, if you want): 1st case: - unset PF_VCPU in kvm_guest_exit(), all the tick is always for system ti= me. Guest time is always 0. 1st case and half: - like 1st case but we move kvm_guest_exit() as you propose and the reaso= n of the interrupt is the tick interrupt. The tick is for guest time only. I t= hink the probability is very low. 2nd case: - don't unset PF_VCPU in kvm_guest_exit(), all the tick is for guest time= =2E I proposed a patch allowing to be more accurate, but it introduces more complexity and system and user time accounting are not very accurate too = (the tick if for system if it appears whereas we are in system, for user if it= appears whereas we are in user). Laurent --=20 ---------------- Laurent.Vivier@bull.net ----------------- "Given enough eyeballs, all bugs are shallow" E. S. Raymond
| Al Boldi | Re: [ck] Re: [ANNOUNCE] RSDL completely fair starvation free interactive cpu sched... |
| Ingo Molnar | Re: [patch] sched_clock(): cleanups |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Denys Vlasenko | [PATCH 1/2] bnx2: factor out gzip unpacker |
