From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Add support for HPET periodic timer. Date: Mon, 13 Aug 2007 11:04:46 +0300 Message-ID: <46C0109E.3090800@qumranet.com> References: <11867779422209-git-send-email-kronos.it@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org To: Luca Tettamanti Return-path: In-Reply-To: <11867779422209-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@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 Luca Tettamanti wrote: > Linux operates the HPET timer in legacy replacement mode, which means that the > periodic interrupt of the CMOS RTC is not delivered (qemu won't be able to use > /dev/rtc). Add support for HPET (/dev/hpet) as a replacement for the RTC; the > periodic interrupt is delivered via SIGIO and is handled in the same way as the > RTC timer. > HPET must be explicitly enabled with -use-hpet. > > Are there any downsides to using HPET? If not, I suggest making it the default, in order to reduce complexity for the user. Something like: - try to use HPET (unless -no-rtc selected) - try to use RTC (unless -no-rtc selected) - fallback to normal unix facilities -- 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/