From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] Add support for HPET periodic timer.
Date: Mon, 13 Aug 2007 11:04:46 +0300 [thread overview]
Message-ID: <46C0109E.3090800@qumranet.com> (raw)
In-Reply-To: <11867779422209-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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/
next prev parent reply other threads:[~2007-08-13 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 20:32 [PATCH] Add support for HPET periodic timer Luca Tettamanti
[not found] ` <11867779422209-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-13 8:04 ` Avi Kivity [this message]
[not found] ` <46C0109E.3090800-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-13 11:50 ` Daniel P. Berrange
[not found] ` <20070813115030.GB14348-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-08-13 17:03 ` Luca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46C0109E.3090800@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox