From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RFC][PATCH] Add HPET emulation to qemu (v2)
Date: Thu, 7 Aug 2008 18:26:00 +0100 [thread overview]
Message-ID: <20080807172600.GU6604@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080807171705.GA15074@implementation.uk.xensource.com>
Samuel Thibault, le Thu 07 Aug 2008 18:17:05 +0100, a écrit :
> Beth Kon wrote some time ago:
> > But for an idle guest in both cases (with and without HPET), the
> > number of wakeups per second was relatively low (28).
>
> Oh, btw, did you try to reduce the qemu window?
Err, maybe it's "minimize" in correct English :)
Samuel
next prev parent reply other threads:[~2008-08-07 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 17:17 [Qemu-devel] Re: [RFC][PATCH] Add HPET emulation to qemu (v2) Samuel Thibault
2008-08-07 17:26 ` Samuel Thibault [this message]
2008-08-07 18:47 ` Anthony Liguori
2008-08-10 1:19 ` Jamie Lokier
2008-08-10 11:01 ` Samuel Thibault
2008-08-10 16:52 ` Jamie Lokier
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=20080807172600.GU6604@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--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).