From: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Dan Kenigsberg <dank-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
Luca Tettamanti
<kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: [PATCH/RFC 0/4] Rework alarm timer infrastrucure.
Date: Thu, 16 Aug 2007 22:41:13 +0200 [thread overview]
Message-ID: <11872968773449-git-send-email-kronos.it@gmail.com> (raw)
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and expands
the alarm timer handling in QEMU. Patches apply to current kvm-userspace tree,
but I think I can rebase it to QEMU svn if desired.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
#ifdefs to handle different timers scattered all over the code I've created a
modular infrastructure where each timer type is self-contained and generic code
is more readable. The resulting code is functionally equivalent to the old one.
Patch 2 implements the "-clock" command line option proposed by Daniel Berrange
and Avi Kivity. By default QEMU tries RTC and then falls back to unix timer;
user can override the order of the timer through this options. Syntax is pretty
simple: -clock timer1,timer2,etc. (QEMU will pick the first one that works).
Patch 3 adds support for HPET under Linux (which is basically my old patch). As
suggested HPET takes precedence over other timers, but of course this can be
overridden.
Patch 4 introduces "dynticks" timer source; patch is mostly based on the work
Dan Kenigsberg. dynticks is now the default alarm timer.
-------------------------------------------------------------------------
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/
WARNING: multiple messages have this Message-ID (diff)
From: Luca Tettamanti <kronos.it@gmail.com>
To: kvm-devel@lists.sourceforge.net
Cc: Dan Kenigsberg <dank@qumranet.com>,
Luca Tettamanti <kronos.it@gmail.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH/RFC 0/4] Rework alarm timer infrastrucure.
Date: Thu, 16 Aug 2007 22:41:13 +0200 [thread overview]
Message-ID: <11872968773449-git-send-email-kronos.it@gmail.com> (raw)
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and expands
the alarm timer handling in QEMU. Patches apply to current kvm-userspace tree,
but I think I can rebase it to QEMU svn if desired.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
#ifdefs to handle different timers scattered all over the code I've created a
modular infrastructure where each timer type is self-contained and generic code
is more readable. The resulting code is functionally equivalent to the old one.
Patch 2 implements the "-clock" command line option proposed by Daniel Berrange
and Avi Kivity. By default QEMU tries RTC and then falls back to unix timer;
user can override the order of the timer through this options. Syntax is pretty
simple: -clock timer1,timer2,etc. (QEMU will pick the first one that works).
Patch 3 adds support for HPET under Linux (which is basically my old patch). As
suggested HPET takes precedence over other timers, but of course this can be
overridden.
Patch 4 introduces "dynticks" timer source; patch is mostly based on the work
Dan Kenigsberg. dynticks is now the default alarm timer.
next reply other threads:[~2007-08-16 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 20:41 Luca Tettamanti [this message]
2007-08-16 20:41 ` [Qemu-devel] [PATCH/RFC 0/4] Rework alarm timer infrastrucure Luca Tettamanti
[not found] ` <11872968773449-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 1/4] " Luca Tettamanti
2007-08-16 20:41 ` [Qemu-devel] " Luca Tettamanti
[not found] ` <11872968771257-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 2/4] Add -clock option Luca Tettamanti
2007-08-16 20:41 ` [Qemu-devel] " Luca Tettamanti
[not found] ` <11872968773155-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 3/4] Add support for HPET periodic timer Luca Tettamanti
2007-08-16 20:41 ` [Qemu-devel] " Luca Tettamanti
[not found] ` <11872968773524-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-16 20:41 ` [PATCH/RFC 4/4] Add support for dynamic ticks Luca Tettamanti
2007-08-16 20:41 ` [Qemu-devel] " Luca Tettamanti
[not found] ` <1187296877557-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-17 7:16 ` Matthew Kent
2007-08-17 7:16 ` [Qemu-devel] Re: [kvm-devel] " Matthew Kent
[not found] ` <42755.207.81.93.54.1187334969.squirrel-N19E6/cp6YFSV923RJcDwA@public.gmane.org>
2007-08-19 8:08 ` Avi Kivity
2007-08-19 8:08 ` [Qemu-devel] Re: [kvm-devel] " Avi Kivity
2007-08-17 12:44 ` [PATCH/RFC 0/4] Rework alarm timer infrastrucure Avi Kivity
2007-08-17 12:44 ` [Qemu-devel] Re: [kvm-devel] " Avi Kivity
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=11872968773449-git-send-email-kronos.it@gmail.com \
--to=kronos.it-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dank-atKUWr5tajBWk0Htik3J/w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.