Searched hist:11629 (Results 1 - 3 of 3) sorted by relevance

/gem5/src/cpu/kvm/
H A Dx86_cpu.cc11629:22f08c96bf7f Tue Sep 13 23:20:00 EDT 2016 Michael LeBeane <michael.lebeane@amd.com> kvm: Support timing accesses for KVM cpu
This patch enables timing accesses for KVM cpu. A new state,
RunningMMIOPending, is added to indicate that there are outstanding timing
requests generated by KVM in the system. KVM's tick() is disabled and the
simulation does not enter into KVM until all outstanding timing requests have
completed. The main motivation for this is to allow KVM CPU to perform MMIO
in Ruby, since Ruby does not support atomic accesses.
H A Dbase.hh11629:22f08c96bf7f Tue Sep 13 23:20:00 EDT 2016 Michael LeBeane <michael.lebeane@amd.com> kvm: Support timing accesses for KVM cpu
This patch enables timing accesses for KVM cpu. A new state,
RunningMMIOPending, is added to indicate that there are outstanding timing
requests generated by KVM in the system. KVM's tick() is disabled and the
simulation does not enter into KVM until all outstanding timing requests have
completed. The main motivation for this is to allow KVM CPU to perform MMIO
in Ruby, since Ruby does not support atomic accesses.
H A Dbase.cc11629:22f08c96bf7f Tue Sep 13 23:20:00 EDT 2016 Michael LeBeane <michael.lebeane@amd.com> kvm: Support timing accesses for KVM cpu
This patch enables timing accesses for KVM cpu. A new state,
RunningMMIOPending, is added to indicate that there are outstanding timing
requests generated by KVM in the system. KVM's tick() is disabled and the
simulation does not enter into KVM until all outstanding timing requests have
completed. The main motivation for this is to allow KVM CPU to perform MMIO
in Ruby, since Ruby does not support atomic accesses.

Completed in 34 milliseconds