Date: Wed, 15 Jan 2014 14:08:01 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com> To: Julian Stecklina <jsteckli@os.inf.tu-dresden.de>, <freebsd-virtualization@freebsd.org> Subject: Re: KVM Clock Message-ID: <52D68831.2000503@citrix.com> In-Reply-To: <lb5thm$3r3$1@ger.gmane.org> References: <lb3jnb$qo8$1@ger.gmane.org> <52D5623C.7060401@freebsd.org> <lb5thm$3r3$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/01/14 13:05, Julian Stecklina wrote: > On 01/14/2014 05:13 PM, Peter Grehan wrote: >> Hi Julian, >> >>> is anyone working on KVM clock support for FreeBSD? If not, I >>> might take a shot at it. >> >> None I know of: go for it :) > > Works for me so far: > https://github.com/blitz/freebsd/commit/cdc5f872b3e48cc0dda031fc7d6bdedc65c3148f Looking > at the code it seems some common routines could be shared between the KVM PV clock and the Xen PV clock (sys/dev/xen/timer/timer.c). The data passed from the hypervisor to the guest has exactly the same format (see struct vcpu_time_info in Xen public headers). At a first sight the KVM clock can benefit from using scale_delta (which is going to be faster than the C version implemented in kvmclock_get_timecount), and xen_fetch_vcpu_tinfo is exactly the same as kvmclock_fetch. Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52D68831.2000503>