From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
jan.kiszka@siemens.com, qemu-devel@nongnu.org, avi@redhat.com,
pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH v4 6/6] qemu_calculate_timeout: increase minimum timeout to 1h
Date: Tue, 31 Jan 2012 16:12:54 +0000 [thread overview]
Message-ID: <1328026374-12803-6-git-send-email-stefano.stabellini@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1201311551120.3196@kaball-desktop>
There is no reason why the minimum timeout should be 1sec, it could
easily be 1h and we would save lots of cpu cycles.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
---
qemu-timer.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/qemu-timer.c b/qemu-timer.c
index de20852..84b970e 100644
--- a/qemu-timer.c
+++ b/qemu-timer.c
@@ -823,6 +823,6 @@ fail:
int qemu_calculate_timeout(void)
{
- return 1000;
+ return 1000*60*60;
}
--
1.7.2.5
prev parent reply other threads:[~2012-01-31 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:11 [Qemu-devel] [PATCH v4 0/6] prevent QEMU from waking up needlessly Stefano Stabellini
2012-01-31 16:12 ` [Qemu-devel] [PATCH v4 1/6] xen: do not initialize the interval timer and PCSPK emulator Stefano Stabellini
2012-01-31 16:12 ` [Qemu-devel] [PATCH v4 2/6] xen: disable rtc_clock Stefano Stabellini
2012-01-31 16:12 ` [Qemu-devel] [PATCH v4 3/6] xen: introduce an event channel for buffered io event notifications Stefano Stabellini
2012-01-31 16:12 ` [Qemu-devel] [PATCH v4 4/6] timers: the rearm function should be able to handle delta = INT64_MAX Stefano Stabellini
2012-01-31 16:12 ` [Qemu-devel] [PATCH v4 5/6] qemu_next_alarm_deadline: check the expire time of a clock only if it is enabled Stefano Stabellini
2012-01-31 16:12 ` Stefano Stabellini [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=1328026374-12803-6-git-send-email-stefano.stabellini@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/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).