Hi everyone, It seems that the KVM enter-exit cycles with 0 instructions executed are caused by the events scheduled from the DRAMCtrl object. The issues is that these events have a very short period which is not sufficient for KvmCPU to even start execution.
I am not familiar with DRAMCtrl memory, it seems that SimpleMemory does not have this issue with KvmCPU. Best regards, On Wed, Jun 11, 2014 at 5:05 PM, Alexandru Duţu <alex.d...@gmail.com> wrote: > Hi all, > > I am trying to understand the current behaviour of KvmCPU. Previous to the > following changeset > > http://repo.gem5.org/gem5/rev/2360411a16be > > after every kvmRun the status was switched to runningService, a new event > was scheduled to the event queue and so with new tick handleKvmExit will be > called. > > However, with the latest changesets on kvm ( > http://repo.gem5.org/gem5/rev/5c2ecad1a3c9) there are a lot of KVM > enter-exit cycles with 0 instructions executed. It seems that the vCPU gets > interrupted by the timer a lot more, which causes kvm to exit without > executing anything. > > An explanation for this behaviour is highly appreciated, is there a need > for timer interrupts that are not allowing the vCPU to actually execute? Or > this might be a side effect of the differences in timers across different > x86 vendors (I am running on an AMD system)? > > Best regards, > -- > Alex > -- Alex _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
