From: <stefano.stabellini@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian.Jackson@eu.citrix.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [PATCH 3/3] increase minimum timeout to 1h
Date: Fri, 18 Nov 2011 14:05:25 +0000 [thread overview]
Message-ID: <1321625125-30726-3-git-send-email-stefano.stabellini@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1111181351190.3519@kaball-desktop>
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
There is no reason why the minimum timeout should be 10s, it could
easily be 1h and we would save lots of cpu cycles.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
---
i386-dm/helper2.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/i386-dm/helper2.c b/i386-dm/helper2.c
index b121e30..c6d049c 100644
--- a/i386-dm/helper2.c
+++ b/i386-dm/helper2.c
@@ -605,8 +605,8 @@ int main_loop(void)
/* Wait up to 10 msec. */
main_loop_wait(10);
#else
- /* Wait up to 10s. */
- main_loop_wait(10000);
+ /* Wait up to 1h. */
+ main_loop_wait(1000*60*60);
#endif
fprintf(logfile, "device model saving state\n");
--
1.7.2.5
next prev parent reply other threads:[~2011-11-18 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 14:04 [PATCH 0/3] prevent qemu-xen-traditional from waking up needlessly Stefano Stabellini
2011-11-18 14:05 ` [PATCH 1/3] xen: introduce an event channel for buffered io event notifications stefano.stabellini
2012-04-03 14:43 ` Ian Jackson
2011-11-18 14:05 ` [PATCH 2/3] xen: don't initialize the RTC timers if xen is available stefano.stabellini
2011-11-18 14:05 ` stefano.stabellini [this message]
2011-12-01 17:56 ` [PATCH 0/3] prevent qemu-xen-traditional from waking up needlessly Ian Jackson
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=1321625125-30726-3-git-send-email-stefano.stabellini@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--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).