From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] Paravirt timer for KVM Date: Mon, 15 Oct 2007 11:07:27 +0200 Message-ID: <47132DCF.3060906@qumranet.com> References: <5d6222a80710120908s6b1f5845head84e7b7a463cd1@mail.gmail.com> <1192218507.14891.18.camel@basalt> <470FD2CA.1000702@codemonkey.ws> <471327C7.8060304@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Jeremy Fitzhardinge , Hollis Blanchard To: Gerd Hoffmann Return-path: In-Reply-To: <471327C7.8060304-H+wXaHxf7aLQT0dZR+AlfA@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 Gerd Hoffmann wrote: > >> 2) the TSC would have to be used as a clocksource. You don't know the >> frequency which is the first problem with using the TSC but some systems >> have a TSC that changes frequencies. >> > > Also note the tsc may stop ticking if the CPU goes sleep in C3, which > IMHO makes the tsc almost useless as clocksource for guests ... > But the host knows that, right? So it can update the guest's timebase? -- 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/