On 02/28/2012 08:16 PM, Alexander Graf wrote:
When we know that we're running inside of a KVM guest, we don't have to
worry about synchronizing timebases between different CPUs, since the
host already took care of that.
This fixes CPU overcommit scenarios where vCPUs could hang forever
On 29.02.2012, at 18:50, Scott Wood scottw...@freescale.com wrote:
On 02/28/2012 08:16 PM, Alexander Graf wrote:
When we know that we're running inside of a KVM guest, we don't have to
worry about synchronizing timebases between different CPUs, since the
host already took care of that.
On 02/29/2012 12:28 PM, Alexander Graf wrote:
On 29.02.2012, at 18:50, Scott Wood scottw...@freescale.com wrote:
On 02/28/2012 08:16 PM, Alexander Graf wrote:
When we know that we're running inside of a KVM guest, we don't have to
worry about synchronizing timebases between different
When we know that we're running inside of a KVM guest, we don't have to
worry about synchronizing timebases between different CPUs, since the
host already took care of that.
This fixes CPU overcommit scenarios where vCPUs could hang forever trying
to sync each other while not being scheduled.
