From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Beth Kon <eak@us.ibm.com>, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC][PATCH] Add HPET emulation to qemu (v2)
Date: Sat, 2 Aug 2008 12:42:29 +0100 [thread overview]
Message-ID: <200808021242.30784.paul@codesourcery.com> (raw)
In-Reply-To: <1217675114-17670-1-git-send-email-eak@us.ibm.com>
> I've been playing with CONFIG_NO_HZ and been surprised by the
> results. I was trying to reproduce the wakeup every 10ms that
> Samuel Thibault mentioned, thinking the HPET would improve it.
> But for an idle guest in both cases (with and without HPET), the
> number of wakeups per second was relatively low (28). Ultimately
> this depends on exactly what the guest is doing
Linux can use the existing acpi PM timer a NO_HZ clocksource.
Paul
prev parent reply other threads:[~2008-08-02 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 11:05 [Qemu-devel] [RFC][PATCH] Add HPET emulation to qemu (v2) Beth Kon
2008-08-02 11:38 ` Samuel Thibault
2008-08-02 14:46 ` Anthony Liguori
2008-08-02 17:21 ` Samuel Thibault
2008-08-02 17:26 ` Samuel Thibault
2008-08-12 16:33 ` Beth Kon
2008-08-02 11:42 ` Paul Brook [this message]
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=200808021242.30784.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=agraf@suse.de \
--cc=eak@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).