On 2015-Jan-04 11:56:14 -0600, Bryan Venteicher bry...@daemoninthecloset.org
wrote:
For the last few weeks, I've been working on adding support for KVM clock
in the projects/paravirt branch. Currently, a KVM VM guest will end up
selecting either the HPET or ACPI as the timecounter source.
On Wed, Jan 21, 2015 at 3:15 PM, Peter Jeremy pe...@rulingia.com wrote:
On 2015-Jan-04 11:56:14 -0600, Bryan Venteicher
bry...@daemoninthecloset.org wrote:
For the last few weeks, I've been working on adding support for KVM clock
in the projects/paravirt branch. Currently, a KVM VM guest
For the last few weeks, I've been working on adding support for KVM clock
in the projects/paravirt branch. Currently, a KVM VM guest will end up
selecting either the HPET or ACPI as the timecounter source. Unfortunately,
this is very costly since every timecounter fetch causes a VM exit. KVM
clock
... so, out of pure curiousity - what's making the benchmark go
faster? Is it userland side of things calling clock methods, or
something in the kernel, or both?
-adrian
On 4 January 2015 at 09:56, Bryan Venteicher
bry...@daemoninthecloset.org wrote:
For the last few weeks, I've been working
On Sun, Jan 4, 2015 at 12:00 PM, Adrian Chadd adr...@freebsd.org wrote:
... so, out of pure curiousity - what's making the benchmark go
faster? Is it userland side of things calling clock methods, or
something in the kernel, or both?
Most likely GEOM statistic gathering in the kernel but
On Sun, Jan 4, 2015 at 8:01 PM, Jim Harris jim.har...@gmail.com wrote:
On Sun, Jan 4, 2015 at 12:00 PM, Adrian Chadd adr...@freebsd.org wrote:
... so, out of pure curiousity - what's making the benchmark go
faster? Is it userland side of things calling clock methods, or
something in the
