From: "M. Warner Losh" <imp@bsdimp.com>
To: avi@redhat.com
Cc: aliguori@us.ibm.com, glommer@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] set migration max downtime
Date: Sun, 24 May 2009 16:40:41 -0600 (MDT) [thread overview]
Message-ID: <20090524.164041.2077911892.imp@bsdimp.com> (raw)
In-Reply-To: <4A19A56D.2020303@redhat.com>
In message: <4A19A56D.2020303@redhat.com>
Avi Kivity <avi@redhat.com> writes:
: Anthony Liguori wrote:
: >> I prefer seconds (and bytes).
: >
: > As a floating point value?
:
: Yes. More than enough spacecraft have been lost due to errors in unit
: conversion.
Floating point values don't have enough resolution to represent
picosecond precision with a unix time-scale range. Had one bug where
a system mysteriously stopped working after the unix epoch got big
enough that it could no longer compute the differences between events
with enough precision to have a stable PLL for the controlled
signals...
Warner
next prev parent reply other threads:[~2009-05-24 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 22:49 [Qemu-devel] [PATCH 0/2] Transfer of funds Glauber Costa
2009-05-21 22:49 ` [Qemu-devel] [PATCH 1/2] add non-arbitrary migration stop condition Glauber Costa
2009-05-21 22:49 ` [Qemu-devel] [PATCH 2/2] set migration max downtime Glauber Costa
2009-05-22 2:09 ` Anthony Liguori
2009-05-24 11:07 ` Avi Kivity
2009-05-24 19:47 ` Anthony Liguori
2009-05-24 19:52 ` Avi Kivity
2009-05-24 22:40 ` M. Warner Losh [this message]
2009-05-22 2:08 ` [Qemu-devel] [PATCH 1/2] add non-arbitrary migration stop condition Anthony Liguori
2009-05-24 8:29 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-05-28 19:22 [Qemu-devel] [PATCH 0/2] Add non-arbitrary treshold for migration Glauber Costa
2009-05-28 19:22 ` [Qemu-devel] [PATCH 1/2] add non-arbitrary migration stop condition Glauber Costa
2009-05-28 19:22 ` [Qemu-devel] [PATCH 2/2] set migration max downtime Glauber Costa
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=20090524.164041.2077911892.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.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).