From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] Paravirt timer for KVM Date: Tue, 16 Oct 2007 11:47:39 +0200 Message-ID: <471488BB.1080205@qumranet.com> References: <5d6222a80710120908s6b1f5845head84e7b7a463cd1@mail.gmail.com> <1192226999.14891.124.camel@basalt> <5d6222a80710151048t22e747l42106a6507c811c6@mail.gmail.com> <1192488895.22523.22.camel@basalt> <5d6222a80710151815m2330c8b7ocf4fc352954a551c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Jeremy Fitzhardinge , Hollis Blanchard To: Glauber de Oliveira Costa Return-path: In-Reply-To: <5d6222a80710151815m2330c8b7ocf4fc352954a551c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Glauber de Oliveira Costa wrote: > I think I'll stick to two fields then, with u64 for seconds and nanoseconds. > Or would it just be better to use a u64 nanoseconds field? > > A _lot_ of time should have passed before such counter overflows. So > having two is possibly overkill u64 nanoseconds looks good to me. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/