[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45EE8315.3020800@vmware.com>
Date: Wed, 07 Mar 2007 01:17:09 -0800
From: Zachary Amsden <zach@...are.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Rusty Russell <rusty@...tcorp.com.au>,
"Nakajima, Jun" <jun.nakajima@...el.com>,
virtualization <virtualization@...ts.osdl.org>,
Roland McGrath <roland@...hat.com>,
Anthony Liguori <anthony@...emonkey.ws>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Jan Beulich <jbeulich@...ell.com>,
Daniel Hecht <dhecht@...are.com>
Subject: Re: Xen & VMI?
Ingo Molnar wrote:
> For example, VMI_CALL_SetAlarm takes a 'cycles' argument. Cycles is a
> quite bad unit for an API, it should be absolute time, nanosec or
> picosec based instead. We could easily see CPUs that have /no concept of
>
Actually, putting the unit in terms of cycles is more portable and
flexible. Rather than perform a conversion from cycles to
nano/femto/pico seconds, the raw cycle count is exposed, along with the
current clock frequency. This allows the timer infrastructure to merely
do one conversion, from cycles to real time, rather than converting to
an arbitrary time unit which may change with operating systems and time
and thus break the ABI.
Zach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists